Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006826Openbravo ERPA. Platformpublic2008-12-18 10:592009-03-26 19:49
Reporteriperdomo 
Assigned Toanthony_wolski 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS20OS Version2.6.23-gentoo-r9
Product Version2.40 
Target VersionFixed 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
Summary0006826: The Accounting Server only posts documents related to one client
DescriptionThe accounting server background process only posts documents of one client.
Steps To ReproduceConstraints:
* Need to have unposted documents on different clients

Steps:
* Apply the patch to your code
* Start tomcat and wait 10 seconds
* Check your catalina.out, you should get something similar to:

No. clients: 6
No. clients: 6
No. clients: 6
processPL - Client: 1000000
No. clients: 6
No. clients: 6
No. clients: 6
No. clients: 6
No. clients: 6
No. clients: 6

Note: 6 is the number of active clients. Only the Client with id 1000000 is processed

Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of backport 00083192.35MP10 closed eduardo_Argal Accounting background process doesn't work when exists more than one client. 
blocks defect 0006639 closed shuehner The Accounting Server only posts documents related to one client 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-01-09 17:58psarobeTypedefect => backport
2009-01-09 17:58psarobefix_in_branch => 2.40
2009-01-10 18:16rafarodaAssigned Torafaroda => anthony_wolski
2009-01-21 14:05shuehnerAssigned Toanthony_wolski => shuehner
2009-01-23 14:28shuehnerAssigned Toshuehner => anthony_wolski
2009-01-26 16:28anthony_wolskiNote Added: 0012630
2009-01-26 16:28anthony_wolskiStatusscheduled => feedback
2009-01-26 16:37anthony_wolskiNote Deleted: 0012630
2009-01-26 16:37anthony_wolskiStatusfeedback => scheduled
2009-01-26 16:37anthony_wolskifix_in_branch2.40 => trunk
2009-01-26 16:38anthony_wolskifix_in_branchtrunk => 2.40
2009-03-24 06:49anthony_wolskiNote Added: 0014880
2009-03-24 06:49anthony_wolskiStatusscheduled => feedback
2009-03-24 11:33iperdomoNote Added: 0014888
2009-03-26 19:49iperdomoRelationship addedduplicate of 0008319
2009-03-26 19:49iperdomoStatusfeedback => closed
2009-03-26 19:49iperdomoDuplicate ID0 => 8319
2009-03-26 19:49iperdomoResolutionopen => duplicate

Notes
(0014880)
anthony_wolski   
2009-03-24 06:49   
This seems to be the correct behaviour. The sampledata only defines one process_scheduling instance, which is for ad_client_id=1000000, ad_org_id=1000000. A check is made for each process() call that selects the ad_process_scheduling line based on the ad_client_id. So the way it currently operates a new process scheduling line needs to be added for each client.

Let me know if I'm mistaken.
(0014888)
iperdomo   
2009-03-24 11:33   
The issue needs to be checked against several clients (at least one different then the one in sampledata), and with accounting process scheduled for each one of them.

I can't test the issue again due a Initial Client Setup issue [1]. When this issue is fixed, I'll try again.

[1] https://issues.openbravo.com/view.php?id=8246 [^]

Cheers,