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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Java Client POS] (No Category)majorrandom2011-07-22 10:572014-04-02 09:04
ReporteradrianromeroView Statuspublic 
Assigned Toadrianromero 
PriorityurgentResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revisionb602618e8ee7
ProjectionnoneETAnoneTarget Version2.40
OSAnyDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release

0018061: Sometimes a deadlock appear when syncrhonizing a and processing orders at the same time

DescriptionWhen launching at the same time the job that imports orders in I_ORDER and the process of orders imported, a deadlock appears and the order imported is not processed automatically and must be manually processed
Steps To ReproduceLaunch the import orders job and the process of orders several times at the same time.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks backport 00180992.50MP33 closedadrianromero Openbravo ERP Sometimes a deadlock appear when syncrhonizing a and processing orders at the same time 

-  Notes
hgbot (developer)
2011-07-27 10:04

Repository: erp/mods/org.openbravo.importdata
Changeset: b602618e8ee7d2c5ccc606106567b18e548a60c4
Author: Adrián Romero <adrianromero <at>>
Date: Tue Jul 26 13:40:08 2011 +0200
URL: [^]

Fixes issue 0018061: Sometimes a deadlock appear when syncrhonizing a and processing orders at the same time
It has been removed two unnecesary foreing keys to avoid the deadlock

M src-db/database/model/tables/I_ORDER.xml
adrianromero (manager)
2011-07-27 14:14
edited on: 2011-07-28 10:26

* Testing the issue

Fill the I_Order table with around 300 valid Order lines. This can be done using the integration job: [^]

Go to the Import Orders window and process the imported orders.

Simultaneously execute the integration job again.

Verify that both processes finish succesfully without any error and also verify that in the AD_PINSTANCE table there is not any execution that registered a deadlock

* Other areas affected

No other areas affected. Only the I_ORDER table definition has been modified.

plujan (manager)
2014-04-02 09:04

Closed as it was in Resolved for too long

- Issue History
Date Modified Username Field Change
2011-07-22 10:57 adrianromero New Issue
2011-07-22 10:57 adrianromero Assigned To => adrianromero
2011-07-22 10:57 adrianromero Status new => scheduled
2011-07-22 10:57 adrianromero fix_in_branch => pi
2011-07-27 10:04 hgbot Checkin
2011-07-27 10:04 hgbot Note Added: 0039421
2011-07-27 10:04 hgbot Status scheduled => resolved
2011-07-27 10:04 hgbot Resolution open => fixed
2011-07-27 10:04 hgbot Fixed in SCM revision => [^]
2011-07-27 13:54 adrianromero fix_in_branch pi =>
2011-07-27 13:56 adrianromero Relationship added blocks 0018099
2011-07-27 14:14 adrianromero Note Added: 0039451
2011-07-28 10:26 adrianromero Note Edited: 0039451 View Revisions
2012-11-07 09:40 priyam Category 02 - ERP-POS Integration => (No Category)
2014-04-02 09:04 plujan Note Added: 0066032
2014-04-02 09:04 plujan Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker