Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027396Retail ModulesWeb POSpublic2014-08-20 20:232014-09-24 19:40
Reporterjecharri 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerOBPS
Support ticket30574
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027396: If the cash up takes more than 4 seconds strange behavior can happen in Cash up
DescriptionIf the cash up takes more than 4 seconds strange behavior can happen in Cash up
Steps To Reproduce-Execute a cash up that it will take more than 4 second

The Web POS will receive success message but the process will continue in the server and also can fail in the server.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0027429RR14Q4 closed Orekaria Stabilization: Revisit the aync timeouts 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-08-20 20:23jecharriNew Issue
2014-08-20 20:23jecharriAssigned To => marvintm
2014-08-20 20:23jecharriOBNetwork customer => Yes
2014-08-20 20:23jecharriSupport ticket => 30574
2014-08-20 20:23jecharriResolution time => 1411509600
2014-08-20 20:23jecharriTriggers an Emergency Pack => No
2014-08-21 01:55eintelauIssue Monitored: eintelau
2014-08-21 01:59eintelauNote Added: 0069554
2014-09-24 19:40marvintmReview Assigned To => marvintm
2014-09-24 19:40marvintmRelationship addedduplicate of 0027429
2014-09-24 19:40marvintmNote Added: 0070320
2014-09-24 19:40marvintmStatusnew => closed
2014-09-24 19:40marvintmResolutionopen => duplicate
2015-03-27 12:58OrekariaRelationship addedblocks 0027329
2015-03-27 12:59OrekariaRelationship deletedblocks 0027329

Notes
(0069554)
eintelau   
2014-08-21 01:59   
Actually what happens is the WebPOS times out the call to the server after 4 seconds. So it never receives the result of the server process (success or failure) and stays on the Loading screen.

In addition, sometimes when this occurs the new cashup records in the WebPOS are not initialised correctly. The cashup record can be created but the paymentmethod cashup records are not. This leaves the POS in a state where future cashups won't work and other functions can also fail.
(0070320)
marvintm   
2014-09-24 19:40   
This issue should be fixed by the change in the timeouts in issue 27429.