2003-01-22 11:31:08,725 ERROR [org.jboss.ejb.BeanLock] Application deadlock detected: TransactionImpl:XidImpl [FormatId=257, GlobalId=redbull//3324, BranchQual=] has deadlock conditions. Two or more transactions contending for same resources and each have locks eachother need.
2003-01-22 11:31:08,728 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException, causedBy: org.jboss.ejb.plugins.lock.ApplicationDeadlockException: Application deadlock detected: Two or more transactions contention. at org.jboss.ejb.plugins.lock.BeanLockSupport.deadlockDetection(BeanLock
Support.java:136) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedP
essimisticEJBLock.java:270) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(Queued
PessimisticEJBLock.java:202) at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPe
ssimisticEJBLock.java:150)
I've read the deadlock section of the docs, but I still don't understand how this situation (separate threads in a remote client) is different from the one in which entirely different clients are making the same requests (in which case I never have problems of this sort).
The other message is this one:
2003-01-22 11:34:34,195 ERROR [STDERR] javax.ejb.TransactionRolledbackLocalException: The iterator of a CMR collection may only be used within the transction in which it was created; CausedByException is:
The iterator of a CMR collection may only be used within the transctionin which it was created
2003-01-22 11:34:34,196 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:224)
2003-01-22 11:34:34,197 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178)
2003-01-22 11:34:34,198 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
I certainly understand the nature of the transcation/iterator restriction, but why would these calls from separate client threads be tickling this?
Again, there must be something I'm just not getting. Shouldn't it be possible to do this?
Thanks for your time and attention on this matter. I look forward to your response.
Beau
Alex Loubyansky wrote:
what is the problem? what locking policy are you using?
alex
Wednesday, January 22, 2003, 8:43:05 PM, you wrote:
BC> I have a Swing app which is essentially single-threaded, accessing the BC> server in the usual way through a session facade. I'd like to do some BC> background loading of certain data for performance reasons, but when I BC> try to do this by using a separate thread (and separate session BC> instance), I get various transaction collision problems if these two BC> threads access the server at the same time.
BC> I'm obviously missing something here--shouldn't different remote client BC> threads from the same client be able to access JBoss simultaneously in BC> the same way that entirely different clients can? I.e., shouldn't they BC> spawn separate transactions which are scheduled appropriately by JBoss?
BC> Any clarification appreciated,
BC> Beau Cronin
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
