In 3.2 and higher, deadlock exceptions are automatically retried. If you're using an earlier version, you'll have to catch and retry on your client.
XXXXXXXXXXXXXXXX Bill Burke Chief Architect JBoss Group, LLC XXXXXXXXXXXXXXXX > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Beau Cronin > Sent: Wednesday, January 22, 2003 3:48 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Can two separate client threads make > simultaneous calls? > > > Complete stack traces are attached. Sorry I didn't give them last time. > > You may well be right about why these deadlocks not occurring with > separate clients. If that's so, is the solution to catch the deadlock > exceptions? > > And any thoughts about the second stack trace (the iterator one)? > > Thanks, > > Beau > > Dan Christopherson wrote: > > > 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) > >> > > ------------------------------------------------------- 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
