Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-1119
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Timothy Bish
Reporter: Jason Sherman
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

Occasional hangs on ensureConnectionInfoSent

Created: 15/Mar/12 03:57 PM   Updated: 19/Mar/12 02:02 PM
Component/s: None
Affects Version/s: 5.5.1-fuse-01-13
Fix Version/s: 5.5.1-fuse-04-01

External Issue URL: https://issues.apache.org/jira/browse/AMQ-2798


 Description  « Hide
Occasionally, it has been reported that the client connections hang and never get a response from the broker.

The following stack trace has been provided:

"main" prio=3 tid=0x0264c800 nid=0x7c waiting on condition [0x38cff000]
   java.lang.Thread.State: WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x8fb5a1b8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
	at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:317)
	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:1286)
	at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1394)
	- locked <0x8fafdd10> (a java.lang.Object)
	at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:506)
	at org.apache.activemq.pool.ConnectionPool.start(ConnectionPool.java:91)
	at org.apache.activemq.pool.PooledConnection.start(PooledConnection.java:78)
	at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:390)
	- locked <0x748e2a80> (a java.lang.Object)
	at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:856)
	at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:838)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:969)
	- locked <0x748e2d58> (a java.lang.Object)
	at java.lang.Thread.run(Thread.java:619)

Apache has a Jira open for this same issue: https://issues.apache.org/jira/browse/AMQ-2798
This is possibly also related to https://issues.apache.org/jira/browse/AMQ-3719



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Jason Sherman added a comment - 15/Mar/12 04:07 PM
Though in most cases the above stack trace would be normal as the client is awaiting a response from the broker, in this case it seems the response is never received.

Timothy Bish added a comment - 19/Mar/12 02:02 PM
Merged fix for https://issues.apache.org/jira/browse/AMQ-3719 into 5.5.x-fuse and 5.5.1-fuse