Application deadlock detected in JBoss 3.2.2RC3

[rafcio]

Hi,

since we use JBoss 3.2.2RC3 we get sometimes:

10:41:06,561 WARN [TxInterceptorCMT] Application deadlock detected retrying 1
11:17:25,338 WARN [TxInterceptorCMT] Application deadlock detected retrying 1
11:17:25,385 WARN [TxInterceptorCMT] Application deadlock detected retrying 1
11:17:25,416 WARN [TxInterceptorCMT] Application deadlock detected retrying 2
11:17:25,588 WARN [TxInterceptorCMT] Application deadlock detected retrying 2

and there one TRACE

2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] Current transaction in MI is TransactionImpl:XidImpl [FormatId=257, GlobalId=rafcio//1381, BranchQual=]
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] TX_MANDATORY for getMandant_id
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] Thread came in with tx TransactionImpl:XidImpl [FormatId=257, GlobalId=rafcio//1381, BranchQual=]
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntityLockInterceptor] Begin invoke, key=2
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntityInstanceInterceptor] Begin invoke, key=2
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntitySynchronizationInterceptor] invoke called for ctx org.jboss.ejb.EntityEnterpriseContext@d0005e, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=rafcio//1377, BranchQual=]
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntityInstanceInterceptor] End invoke, key=2, ctx=org.jboss.ejb.EntityEnterpriseContext@d0005e
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntityLockInterceptor] End invoke, key=2
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.LogInterceptor] End method=getMandant_id
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.EntityLockInterceptor] End invoke, key=2
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.LogInterceptor] End method=getMandant_id
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.StatelessSessionInstancePool] Discard instance:org.jboss.ejb.plugins.StatelessSessionInstancePool@63ae08#org.jboss.ejb.StatelessSessionEnterpriseContext@1ba92bb#TransactionImpl:XidImpl [FormatId=257, GlobalId=rafcio//1373, BranchQual=]#true#class net.magix.ejb.keyword.sessionbeans.KeywordFacade
2003-09-14 15:58:34,796 TRACE [org.jboss.ejb.plugins.TxInterceptorCMT] TxInterceptorCMT: In finally
2003-09-14 15:58:34,796 WARN [org.jboss.ejb.plugins.TxInterceptorCMT] Application deadlock detected retrying 1

Our client is sending an Request thru HTTP to an Servlet, which is calling an special stateless session bean facade (transaction is set to Required). This session bean check some permissions and the data, than is calling other stateless session bean facade with the given business logic (transaction is set to Required). The business logic uses entity beans (transaction for the entity beans is set to Mandatory and all get methods are read-only).

Is this an knowing problem in RC3?


Best Regards,
Rafal

[rafcio]

I get an answer from Scott Stark:

"Yes, the deadlock detection logic does have a problem that can cause spurious warnings in 3.2.2RC3. This has been fixed and will be in the 3.2.2RC4 due out next week.

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx"


Regards,
Rafal