You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/09/16 11:39:09 UTC
[jira] [Commented] (AMQ-3495) Active MQ 5.4.2 - Message stuck due
to connection hung for amq client
[ https://issues.apache.org/jira/browse/AMQ-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105964#comment-13105964 ]
Gary Tully commented on AMQ-3495:
---------------------------------
so that stack trace indicates that it is waiting for a commit reply from the broker, do you have a corresponding thread dump from the broker to see why that request is blocked?
> Active MQ 5.4.2 - Message stuck due to connection hung for amq client
> ---------------------------------------------------------------------
>
> Key: AMQ-3495
> URL: https://issues.apache.org/jira/browse/AMQ-3495
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Environment: RedHat Linux 2.6.18-194.11.1.el5
> AMQ 5.4.2
> WebSphere Application Server 7.0
> Reporter: Rahul Shinge
> Priority: Blocker
>
> Hi - Here is high level overview of response flow using Active MQ
> Destination System JMS Client -> AMQ Response Queue -> Firewall -> Source System JMS Client
> Firewall timeout = 30 min
> Current volume = approx 6400 messages/day -- 400 messages/10 min
> Source system JMS (WebSphere) client is connected to AMQ Broker using JMS API and AMQ 5.4.2 libraries. We are experiencing intermittent issue in PRODUCTION -- Source system client connection gets hung and requires restart to process pending message on queue. At this point we are not able to reproduce this issue at will but it occurs in PRODUCTION intermittently.
> Here is tracing from Websphere client which shows org.apache.activemq.ActiveMQSession.commit was called but didn't succeed.
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:173)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer
> $ConditionObject.await(AbstractQueuedSynchronizer.java:1937)
> at java.util.concurrent.ArrayBlockingQueue.take
> (ArrayBlockingQueue.java:329)
> at org.apache.activemq.transport.FutureResponse.getResult
> (FutureResponse.java:40)
> at org.apache.activemq.transport.ResponseCorrelator.request
> (ResponseCorrelator.java:87)
> at org.apache.activemq.ActiveMQConnection.syncSendPacket
> (ActiveMQConnection.java:1276)
> at org.apache.activemq.TransactionContext
> .syncSendPacketWithInterruptionHandling(TransactionContext.java:704)
> at org.apache.activemq.TransactionContext.commit
> (TransactionContext.java:299)
> at org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:560)
> at com.ibm.ejs.jms.JMSManagedSession$JMSLocalTransaction.commit
> (JMSManagedSession.java:1203)
> at com.ibm.ejs.j2c.LocalTransactionWrapper.commit
> (LocalTransactionWrapper.java:263)
> at com.ibm.tx.jta.OnePhaseResourceImpl.commit_one_phase
> (OnePhaseResourceImpl.java:140)
> at com.ibm.tx.jta.RegisteredResources.flowCommitOnePhase
> (RegisteredResources.java:2297)
> at com.ibm.tx.jta.RegisteredResources.commitLastAgent
> (RegisteredResources.java:3067)
> at com.ibm.tx.jta.TransactionImpl.prepareResources
> (TransactionImpl.java:1463)
> at com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing
> (TransactionImpl.java:514)
> at com.ibm.tx.jta.TransactionImpl.processCommit
> (TransactionImpl.java:978)
> at com.ibm.tx.jta.TransactionImpl.commit(TransactionImpl.java:913)
> at com.ibm.ws.tx.jta.TranManagerImpl.commit(TranManagerImpl.java:377)
> at com.ibm.tx.jta.TranManagerSet.commit(TranManagerSet.java:161)
> at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:927)
> at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:230)
> at com.ibm.ejs.csi.TransactionControlImpl.postInvoke
> (TransactionControlImpl.java:570)
> at com.ibm.ejs.csi.UOWControlImpl.postInvoke(UOWControlImpl.java:384)
> at com.ibm.ejs.container.EJSContainer.postInvoke
> (EJSContainer.java:4558)
> at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:111)
> at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:136)
> at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:242)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
> at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:979)
> at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage
> (ServerSession.java:1064)
> at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:560)
> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
> Please let me know if you have seen this issue and need additional information.
> Regards,
> Rahul
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira