[jboss-user] [JBossMQ] - Re: Deadlock race-condition committing JBossMQ txn

janush do-not-reply at jboss.com
Wed May 6 10:13:01 EDT 2009


Adrian, I applied the changes from JBAS-5801 because I had illegal monitor state exceptions in JBoss 4.2.3  too.
But, java.lang.IllegalMonitorStateException appears again, in another method:

  | java.lang.IllegalMonitorStateException
  |         at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:127)
  |         at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1175)
  |         at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:431)
  |         at org.jboss.resource.adapter.jms.JmsManagedConnection.unlock(JmsManagedConnection.java:416)
  |         at org.jboss.resource.adapter.jms.JmsXAResource.end(JmsXAResource.java:76)
  |         at org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper.end(JcaXAResourceWrapper.java:58)
  |         at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.endSuspendedRMs(TransactionImple.java:1529)
  |         at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImple.java:235)
  |         at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501)
  |         at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:361)
  |         at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
  |         at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
  |         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
  |         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
  |         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
  |         at org.jboss.ejb.Container.invoke(Container.java:960)
  |         at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
  |         at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
  | 
Is the only way to avoid it is to use track-connection-by-tx?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229036#4229036

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229036



More information about the jboss-user mailing list