I'm using OJB 1.0 rc4 inside of jboss3.2.2rc3 and db2.
OJB is running into self generated deadlocks if I access ojb with concurrent ejb clients when using SequenceManagerNextValImpl
As a workaround I use SequenceManagerInMemoryImpl but I think this won't work with sequences.
If ojb could access his internal tables with read uncommitted this should not
occur but it seems that OJB does not commit it's entries at the internal tables, especially the sequence id's.
What can I do to get rid of the deadlocks?
best regards,
Guido
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
