Re: [JBoss-user] Can two separate client threads make simultaneouscalls?

[Dan Christopherson]

These deadlocks are most likely on your entity beans (the second one is fishy looking, but I really can't say much without seeing more (all) of the stack trace.). By default, JBoss only keeps one instance per bean identity, so each transaction from your client will block on the entity. Give the full stack trace, that might be helpful.

launching from different client app instances will change the timings of things, making the deadlock less likely, but perhaps still possible, depending on your application.

Beau Cronin wrote:

There are two messages which appear. The first is:

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)

smime.p7s
Description: S/MIME Cryptographic Signature