I tryied to reproduce this with 3.2.2RC2, but thre we don't get any deadlock detection warning. This we can see in server log in TRACE mode:
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 [EMAIL PROTECTED], 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, [EMAIL PROTECTED]
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:[EMAIL PROTECTED]@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 send at the same time 4-6 requests to the server. all are only get requests. Is this an bug in JBoss 3.2.2RC3 ?
Regards, Rafal At 12:03 12.09.2003 +0200, Rafal Kedziorski wrote:
hi,
since we use JBoss 3.2.2RC3 we get this warnings:
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 11:17:25,650 WARN [TxInterceptorCMT] Application deadlock detected retrying 3 11:17:25,947 WARN [TxInterceptorCMT] Application deadlock detected retrying 3 11:17:27,322 WARN [TxInterceptorCMT] Application deadlock detected retrying 1 11:25:16,018 WARN [TxInterceptorCMT] Application deadlock detected retrying 1 11:48:30,605 WARN [TxInterceptorCMT] Application deadlock detected retrying 1 11:48:32,887 WARN [TxInterceptorCMT] Application deadlock detected retrying 1 11:52:35,815 WARN [TxInterceptorCMT] Application deadlock detected retrying 1
with JBoss 3.2.2RC2 there warn't any problem. Is this JBoss problem or problem in our Application. This messages we gets while testing our application only by one user. Our client sends thru HTTP an XML request to the servlet, which is calling a session facade. This call other session bean which use some entity beans.
Regards, Rafal
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
