Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0039045Retail ModulesWeb POSpublic2018-07-25 12:402018-07-25 12:40
Reportermtaal 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionpiFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0039045: DataSynchronizationProcess commits the work and related import entry in different transactions
DescriptionThe DataSynchronizationProcess does a commit of the work first [1] and then sets the related importentry to processed [2] in a separate transaction. If the server is stopped/blocked/error in between the import entry will remain at initial status and will be reprocessed.

[1]
https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/tip/src/org/openbravo/mobile/core/process/DataSynchronizationProcess.java#l224 [^]

[2]
https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/tip/src/org/openbravo/mobile/core/process/DataSynchronizationProcess.java#l277 [^]
Steps To ReproduceSet a breakpoint at the commit
Do a cashup
Step over the commit
Stop the server
Restart
Import entry is reprocessed but as the cashup was already processed an error is set in obpos_errors
Proposed SolutionCombine the commits/set processed in one transaction
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-07-25 12:40mtaalNew Issue
2018-07-25 12:40mtaalAssigned To => Retail
2018-07-25 12:40mtaalOBNetwork customer => No
2018-07-25 12:40mtaalTriggers an Emergency Pack => No

There are no notes attached to this issue.