[jboss-user] [JBoss Messaging] - Threads Hanging Indefinitely in ClosedInterceptor
zackurey
do-not-reply at jboss.com
Fri Jul 11 01:09:29 EDT 2008
Hi,
I've been running into some intermittent issues where threads publishing messages are waiting forever in ClosedInterceptor.checkCloseAlreadyDone.
Environment:
Client Server: JBoss 4.2.2GA using the JMSRA
Broker Server: JBoss 4.2.2GA, JBoss Messaging 1.4.0.SP3
The only current work around I have right now is to bounce my application as the thread is never let free. The only thing I can think of is that somehow inUseCount never gets down to 0.
The broker isn't under heavy load with messages only being published every 4 hours by the threads that are getting stuck, and one other thread that is pinging for availability every 30 seconds. Again this is very random, I've seen it run for a week with no issues, and other times it happens nearly immediately.
Doing a thread-dump I see:
"QuartzScheduler_Worker-8" prio=1 tid=0x198c6640 nid=0x259e in Object.wait() [0x19279000..0x19279e20]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at org.jboss.jms.client.container.ClosedInterceptor.checkCloseAlreadyDone(ClosedInterceptor.java:245)
- locked <0x37d7fd18> (a org.jboss.jms.client.container.ClosedInterceptor)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:142)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$close_N4742752445160157748.invokeNext(ClientConnectionDelegate$close_N4742752445160157748.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.close(ClientConnectionDelegate.java)
at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:203)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:124)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeNext(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeNext(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java)
at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:637)
at org.jboss.jms.tx.ResourceManager.commit(ResourceManager.java:370)
at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:238)
at org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper.commit(JcaXAResourceWrapper.java:53)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:636)
at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2619)
at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1779)
- locked <0x37d7d108> (a com.arjuna.ats.internal.jta.transaction.arjunacore.AtomicAction)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:842)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:662)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:632)
Are there any previous issues resolved that could be related to this that have a work around or patch that anyone knows of?
Thanks in advance.
Zach
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163750#4163750
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163750
More information about the jboss-user
mailing list