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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Web POSmajoralways2020-12-14 09:302020-12-31 07:47
Reportersalvador_campanellaView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0045562: Messages, translations and lists for all modules are loaded from the database every time WebPOS is accessed or refreshed in HA

DescriptionMessages, translations, and lists for all modules are loaded from the database every time WebPOS is accessed or refreshed in High Availability instances

As part of the initial loading steps of WebPOS, there are some pre-render actions that include loading all the messages, translations, and lists. This information is not cached so the same results are loaded from the database many times.

When having two nodes for the Application Server, when we login back office on node-A, and update the translation, only node-A Labels Map cleared. The translations only affect the tills linked to node-A, the tills linked on Node-B will not be affected.
Steps To Reproduce- Add a breakpoint in in functions getLabels() in line 'for (Object[] qryTrlObject : qryLists.list()) {'
- Load the WebPOS login screen (the breakpoint is hit)
- Refresh the page (the breakpoint is hit again)
- Load the WebPOS login screen from another computer (the breakpoint is hit again)
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0042356 closedranjith_qualiantech_com Messages, translations and lists for all modules are loaded from the database every time WebPOS is accessed or refreshed 

-  Notes
marvintm (developer)
2020-12-31 07:47

We are changing this issue to design defect.

Translations are considered "sources" in OB, and that is why they are cached. It is true that as part of the caching mechanism we also introduced an event handler to reset the cache whenever possible, but this didn't change the fact that the correct way to apply a translation in a production environment in Openbravo is by installing a translation module, and this has always required a system restart.

Changing this rule (so essentially removing the cache as there is no way to properly reset it in a HA environment), would be worse decisions overall than removing this limitation because of the performance penalty they would introduce, so we have decided not to change it for now.

- Issue History
Date Modified Username Field Change
2020-12-14 09:30 salvador_campanella New Issue
2020-12-14 09:30 salvador_campanella Assigned To => Retail
2020-12-14 09:30 salvador_campanella Triggers an Emergency Pack => No
2020-12-14 09:30 salvador_campanella Relationship added related to 0042356
2020-12-31 07:47 marvintm Note Added: 0125200
2020-12-31 07:47 marvintm Type defect => design defect

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker