Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027943Retail ModulesWeb POSpublic2014-10-22 10:232014-12-10 13:38
Reporteregoitz 
Assigned Tomtaal 
PriorityimmediateSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR15Q1 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027943: The OrderLoader process produce locks on the ad_sequence table.
DescriptionThe OrderLoader process produce locks on the ad_sequence table.
With high concurrency the locks can affect the performance.
Steps To Reproduce-Use simultanously several pos terminal with the same pos terminal type.
- As they use the same documenttype locks happens if the process sync is done at the same time.
*It can happen if the devides are offline for a while and all of them go back online at the same time. ON that moment all the pos are synchronized.
Proposed Solution-Take the documentno at the end of the process.
Similar than what was done on the ticket:
https://issues.openbravo.com/view.php?id=27638 [^]
Additional Information
TagsNo tags attached.
Relationships
related to defect 0027638 closed marvintm The cashup process takes long in some cases and causes locks on the database 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-22 10:23egoitzNew Issue
2014-10-22 10:23egoitzAssigned To => marvintm
2014-10-22 10:23egoitzResolution time => 1414274400
2014-10-22 10:23egoitzTriggers an Emergency Pack => No
2014-10-22 10:23egoitzRelationship addedrelated to 0027638
2014-11-03 14:59mario_castelloAssigned Tomarvintm => mario_castello
2014-11-03 14:59mario_castelloStatusnew => scheduled
2014-11-03 14:59mario_castellofix_in_branch => pi
2014-11-05 17:24mtaalAssigned Tomario_castello => mtaal
2014-11-30 23:54mtaalNote Added: 0072168
2014-11-30 23:55hgbotCheckin
2014-11-30 23:55hgbotNote Added: 0072169
2014-11-30 23:55hgbotStatusscheduled => resolved
2014-11-30 23:55hgbotResolutionopen => fixed
2014-11-30 23:55hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/72727143c4da1d2df1df748c7d55093bad56e3c1 [^]
2014-12-01 00:03mtaalNote Added: 0072170
2014-12-10 13:38marvintmReview Assigned To => marvintm
2014-12-10 13:38marvintmStatusresolved => closed
2014-12-10 13:38marvintmFixed in Version => RR15Q1

Notes
(0072168)
mtaal   
2014-11-30 23:54   
After researching there are 2 documentnos retrieval which can be postponed to later in the transaction: invoice and shipment.
The order doc no is already set when it reaches the server. The payment plan document number must be set as when the payment plan is done triggers are enabled and the document no can not be set later.
(0072169)
hgbot   
2014-11-30 23:55   
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 72727143c4da1d2df1df748c7d55093bad56e3c1
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Sun Nov 30 23:55:19 2014 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/72727143c4da1d2df1df748c7d55093bad56e3c1 [^]

Fixes issue 27943: The OrderLoader process produce locks on the ad_sequence table.
Move setting of the document number as late as possible in the flow, only invoice
and shipment document number can be moved there, order doc no is already
set and payment plan document number can't be changed.

---
M src/org/openbravo/retail/posterminal/OrderLoader.java
---
(0072170)
mtaal   
2014-12-01 00:03   
I did a test using jmeter, with 30 users each syncing 10 orders simultaneously. On a fast laptop without optimization of database or other things this took 1-2 minutes in total with throughput times of each request between 30-40 seconds.