James,
I uploaded a patch that might fix your problem:
https://issues.apache.org/jira/browse/OFBIZ-3557
-Adrian
On 5/20/2010 10:31 AM, James McGill wrote:
On Wed, May 19, 2010 at 9:53 PM, David E Jones<[email protected]> wrote:
It's all about locking and blocking...
The scenario you describe is probably fairly rare
Probably, but it has hit us several times, and we don't have a lot of users
on this. When it breaks, it stays broken until someone updates
PartyAcctgPreference.
For cases where two threads do manage to both get a query in to prevent the
problem in the db thread A could do a select for update (causing a lock if
the db cooperates)
I don't think minilang provides this much control. How do you do select
for update via the delegator?
SequenceUtil relies on JVM synchronization, so that should work for this
also.
James