Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012401Openbravo ERPA. Platformpublic2010-02-22 17:322010-03-16 00:00
Reporternetworkb 
Assigned Toshuehner 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS30OS Version
Product Versionmain 
Target Version2.50MP14Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012401: After a while execuing a process the session is closed before return any result of the execution
DescriptionAfter a while execuing a process the session is closed before return any result of the execution.
If i execute a process that takes long, the session of the user is closed and you don't receive any result.
Steps To Reproduce-Install the idl module.
-Try to import a file with 260.000 rows.
-After wait for a long time, if you see the openbravo log you will see that the session of the users is closed but the application shows a window that says that the process is still running.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0012542 new jonalegriaesarte Modules IDL validation process (for at least the product price entity) executes too many (duplicate) database-queries 
related to defect 0012543 new jonalegriaesarte Modules The long-running IDL validation process (at least) should get a progress bar. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-02-22 17:32networkbNew Issue
2010-02-22 17:32networkbAssigned To => alostale
2010-02-22 17:53alostaleAssigned Toalostale => shuehner
2010-02-22 17:59networkbSeveritycritical => major
2010-02-22 18:13networkbNote Added: 0024708
2010-02-22 18:49pjuvaraNote Added: 0024710
2010-02-23 08:16alostaleRelationship addedrelated to 0012362
2010-02-23 08:16alostaleNote Added: 0024719
2010-02-23 08:16alostaleStatusnew => scheduled
2010-02-23 08:16alostalefix_in_branch => pi
2010-02-23 09:46networkbPriorityimmediate => urgent
2010-02-23 09:46networkbTarget Version2.50MP12 => 2.50MP13
2010-02-23 09:46networkbfix_in_branchpi =>
2010-03-03 17:47shuehnerRelationship addedrelated to 0012542
2010-03-03 17:47shuehnerNote Added: 0025021
2010-03-03 17:47shuehnerRelationship deletedrelated to 0012362
2010-03-03 17:49shuehnerRelationship addedrelated to 0012543
2010-03-08 16:05jpabloaeTarget Version2.50MP13 => 2.50MP14
2010-03-15 19:16shuehnerNote Added: 0025494
2010-03-15 19:16shuehnerStatusscheduled => closed
2010-03-15 19:16shuehnerResolutionopen => no change required
2010-03-16 00:00anonymoussf_bug_id0 => 2970932

Notes
(0024708)
networkb   
2010-02-22 18:13   
After get this error, if you go to the window where the rows imported should appear, you get the following error:

Error:
Los datos pueden estar incompletos porque el servidor no replicó a la hora especificada. Compruebe la conexión con el servidor.
(0024710)
pjuvara   
2010-02-22 18:49   
How can the target be 2.50MP12?
(0024719)
alostale   
2010-02-23 08:16   
Reminder sent to: shuehner

Is this issue related with 0012362?
(0025021)
shuehner   
2010-03-03 17:47   
No, not related to 12362 but standard ERP behavior with regard to session timeout.
(0025494)
shuehner   
2010-03-15 19:16   
In agreement with gps-team and partner marking as closed as the behavior is standard-timeout and the following workaround exist:

Don't import all 260k rows at once but in smaller batches to get the runtime per batch below the standard timeout of 60min.

To improve the performance and usability of the IDL import process two new issues have been scheduled to a.) make the validation/import faster and b.) add a progress bar to report the current validation/import state to the user (this second issue will effectively remove the session-timeout problem also)