Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Mobile Warehouse operationsmajoralways2021-07-16 17:112021-08-04 17:48
ReporterlbressanView Statuspublic 
Assigned Torqueralta 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned Toadrianromero
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0047406: Open session issue

DescriptionOpen session windows on backoffice with system role, log in AWO session as a guest and close the browser, then the session keeps open.
Steps To ReproduceSteps:

1- Open "Session" windows on backoffice as System Administrator.
2- Log in AWO Session as a guest and close the browser.
3- The session keeps open.

Here's a link with the steps in a video: [^]
TagsNo tags attached.
Attached Filespng file icon opensessions.png [^] (134,901 bytes) 2021-08-04 14:53

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
Practics (reporter)
2021-07-16 17:16

AƱadir que la sesiones de cliente (mobile) no se cierran con timeout con lo cual esas sesiones nunca llegan a cerrarse
adrianromero (manager)
2021-08-04 14:49

Looking at the video, when the browser is closed tapping on the close icon, the session will stay open until the configured timeout is reached. This is the expected behaviour.

About the timeout we are observing also it is working as expected in livebuilds. We cannot reproduce the behaviour of sessions open forever. Sessions are deleted as expected when the timeout is reached. In the image attached it can be observed that livebuilds do not have sessions older than one hour. Livebuilds sessions timeout is 60 minutes.

Note that configuring the session timeout requires not only configuring the timeout in the dictionary but also to recompile, regenerate web.xml and restart tomcat as explained in the documentation. [^]

Can you please verify and send to us the following to check the issue in your environment?

1.- The timeout configuration in AD Implementation Mapping and generated web.xml?
2.- An screenshot of the Sessions window with sessions older than the configured timeout?

Practics (reporter)
2021-08-04 16:47

I tried again and it works fine, maybe the web.xml was not generated correctly

- Issue History
Date Modified Username Field Change
2021-07-16 17:11 lbressan New Issue
2021-07-16 17:11 lbressan Assigned To => Retail
2021-07-16 17:11 lbressan Resolution time => 1627596000
2021-07-16 17:11 lbressan Triggers an Emergency Pack => No
2021-07-16 17:15 Practics Issue Monitored: Practics
2021-07-16 17:16 Practics Note Added: 0130548
2021-07-26 22:34 rqueralta Assigned To Retail => rqueralta
2021-07-26 22:34 rqueralta Status new => scheduled
2021-08-04 14:49 adrianromero Note Added: 0130975
2021-08-04 14:49 adrianromero Status scheduled => feedback
2021-08-04 14:53 adrianromero File Added: opensessions.png
2021-08-04 16:47 Practics Note Added: 0130976
2021-08-04 17:48 adrianromero Review Assigned To => adrianromero
2021-08-04 17:48 adrianromero Status feedback => closed
2021-08-04 17:48 adrianromero Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker