Guillaume Nodet wrote:
When using two instances of ojb on different data sets, but using the same table for SequenceManagerHighLowImpl, i ran into an optimistic lock error. I took a look at the code, and i see there were 5 retries to test for achieving the select / store process. My question is: as the HighLowSequence is cached by the cache implementation, shouldn't it be necessary to remove it from the cache before retrying the process ? I suppose that the cache returns the same object every times it is queried so the process will fail at each new attempt.
Which version of OJB do you use? Normally in repository_internal.xml of HighLowSequence class-descriptor the empty cache implementation was declared, thus objects should never be cached.
...
<class-descriptor
class="org.apache.ojb.broker.util.sequence.HighLowSequence"
table="OJB_HL_SEQ"
><object-cache class="org.apache.ojb.broker.cache.ObjectCacheEmptyImpl">
</object-cache>
...
regards, Armin
Regards,
Guillaume Nodet
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
