JBoss Developer: Message List - Server becomes nonresponsive after several Transaction TimeoMost recent forum messageshttps://developer.jboss.org/community/jbossas/persistence?view=discussionsJive Engage2004-05-27T07:22:15Z2004-05-27T07:22:15ZenRe: Server becomes nonresponsive after several Transaction TAlexey Loubyansky/people/aloubyanskydo-not-reply@jboss.com2004-05-27T07:22:15Z2004-05-27T07:22:15Z<!-- [DocumentBodyStart:1d03b953-ad22-4b99-ae7a-935f2fb18e3e] --><div class="jive-rendered-content"><p>1) Are there still deadlock situations that JBoss cannot predict or detect?<br/><br/>Yes. For example, when an instance is locked in a transaction then we call a method with RequiresNew and that new transaction tries to lock the instance that was locked by the previous not yet committed transaction.<br/>A deadlock might also occur in other non-EJB layers like database and shared resources.<br/><br/>2) Is it possible, that even while using Instance Per Transaction with JBoss, for all Entity Beans to become locked?<br/><br/>Not in EJB layer except for the case above with when the same thread accesses same instances from different transactinal contexts (see above).<br/><br/>3) Is there a good way to debug this sort of problem?<br/><br/>You can increase log level to TRACE (see log4j.xml for example) for org.jboss.ejb.plugins and org.jboss.tm. And analyse thread dumps.</p></div><!-- [DocumentBodyEnd:1d03b953-ad22-4b99-ae7a-935f2fb18e3e] --><img src='/beacon?t=1521468840056' />2004-05-27T07:22:15Z13 years 10 months ago0Re: Server becomes nonresponsive after several Transaction Tspetter/people/spetterdo-not-reply@jboss.com2004-05-26T22:00:12Z2004-05-26T22:00:12Z<!-- [DocumentBodyStart:0f25803b-605d-4e8a-a286-3c34dcb9914a] --><div class="jive-rendered-content"><p>Additional information:<br/><br/>Our transaction timeout is set to 1 hour.</p></div><!-- [DocumentBodyEnd:0f25803b-605d-4e8a-a286-3c34dcb9914a] -->2004-05-26T22:00:12Z13 years 10 months ago0Server becomes nonresponsive after several Transaction Timeospetter/people/spetterdo-not-reply@jboss.com2004-05-26T21:47:05Z2004-05-26T21:47:05Z<!-- [DocumentBodyStart:eedd3751-c18f-48b7-809b-aaa34e5e282f] --><div class="jive-rendered-content"><p>I have an application that is able to function continously for many days without any problems. Suddenly, the application stops processing, and we start getting several occurances of the following message/warning:<br/><br/>10:42:37,961 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl [Format<br/>Id=257, GlobalId=HQ-ALL25//29, BranchQual=] timed out. status=STATUS_ACTIVE<br/><br/>From reading the forums, we know this is usually an indication that a deadlock situation has occurred. However, we are unable to see the usual ApplicationDeadlockException.<br/><br/><strong>Application information:</strong><br/>1) We are using JBoss version 3.2.1.<br/>2) Our bean execution chain is MDB--&gt;SLSB--&gt;Entity Bean (CMP).<br/>3) We are using Instance Per Transaction to solve our deadlock problems.<br/>4) We already upgraded to the latest version of concurrent.jar (1.3.3) to solve previously reported MDB message reception problems.<br/><br/><strong>Here are my questions:</strong><br/>1) Are there still deadlock situations that JBoss cannot predict or detect?<br/>2) Is it possible, that even while using Instance Per Transaction with JBoss, for all Entity Beans to become locked? (Resulting in a non-responsive server)<br/>3) Is there a good way to debug this sort of problem?<br/><br/>Any help is greatly appreciated!<br/>Thanks,<br/>Julie</p></div><!-- [DocumentBodyEnd:eedd3751-c18f-48b7-809b-aaa34e5e282f] -->2004-05-26T21:47:05Z13 years 10 months ago20