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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Retail Modules] Web POSmajoralways2018-01-15 18:532018-01-24 14:24
ReportermarvintmView Statuspublic 
Assigned Tomarvintm 
PriorityurgentResolutionfixedFixed in VersionRR17Q4.1
StatusclosedFix in branchFixed in SCM revisionf87bcc98aa2a
ProjectionnoneETAnoneTarget VersionRR17Q4.1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomigueldejuana
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0037646: LogClient should not be sent if session is not valid

DescriptionCurrently logclient is always sent, even if the WebPOS already detected that session is no longer valid, and that the user must log in again. This wastes network bandwidth, which can in some cases be problematic.

Instead, the process should not be run if the session is not valid, and should only be restarted when the user logs in again.
Steps To Reproduce- Log in the WebPOS, with the "Network" tab in developer tools open.
- Restart tomcat (to force session lost)
- Wait some time.
- At some point, the WebPOS detects that the session is lost, and shows the popup that explains the user that he needs to log in again.
- Wait more time. Check the "Network" tab, and realize that the log client request is still triggered periodically. This doesn't make sense, as it wastes bandwidth without any chance of succeeding.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0037644 closedmarvintm LogClient should not be sent if session is not valid 

-  Notes
hgbot (developer)
2018-01-22 13:53

Repository: retail/backports/3.0RR17Q4.1/
Changeset: f87bcc98aa2af5adfcf17d26bd74e71dabec740e
Author: Antonio Moreno <antonio.moreno <at>>
Date: Mon Jan 22 13:52:24 2018 +0100
URL: [^]

Fixed issue 37646. LogClient request will no longer happen if session was lost. Added API to enable/disable log client process, with two main goals:
-Disable the interval when session is lost, to remove unnecessary overhead
-Try to prevent potential duplicate calls to the log client process

M web/
M web/
M web/
M web/
migueldejuana (developer)
2018-01-24 14:24

Tested and reviewed

- Issue History
Date Modified Username Field Change
2018-01-15 18:53 marvintm Type defect => backport
2018-01-15 18:53 marvintm Target Version => RR17Q4.1
2018-01-22 11:19 marvintm Assigned To Retail => marvintm
2018-01-22 13:53 hgbot Checkin
2018-01-22 13:53 hgbot Note Added: 0101841
2018-01-22 13:53 hgbot Status scheduled => resolved
2018-01-22 13:53 hgbot Resolution open => fixed
2018-01-22 13:53 hgbot Fixed in SCM revision => [^]
2018-01-24 14:24 migueldejuana Review Assigned To => migueldejuana
2018-01-24 14:24 migueldejuana Note Added: 0101923
2018-01-24 14:24 migueldejuana Status resolved => closed
2018-01-24 14:24 migueldejuana Fixed in Version => RR17Q4.1

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker