You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Grant H <de...@td-tech.com> on 2006/05/17 09:42:50 UTC

Blocks on the method MutexTransport.oneaway

Phenomenon 1

When using mq4.0-rc2 version to send messages, the following problems will
occur.
The thread sent by messages stays on the method of CountDownLatch.await,
which results in unsuccessful sending of following messages. And it blocks
on the method of MutexTransport.oneaway, which waits for the previous
successful sending message.

Name: RMI TCP Connection(4)-192.168.167.2
State: WAITING on
edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch@1e6978d
Total blocked: 1  Total waited: 1

Stack trace: 
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:474)
edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:179)
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:73)
org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:356)
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:63)
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:68)
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1108)
org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1196)
org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:252)
org.apache.activemq.pool.SessionPool.createSession(SessionPool.java:116)
org.apache.activemq.pool.SessionPool.makeObject(SessionPool.java:84)
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
org.apache.activemq.pool.SessionPool.borrowSession(SessionPool.java:59)
com.shjv.tdscdma.omc.common.message.activemq.PooledConnection$CustomConnectionPool.createSession(PooledConnection.java:217)
com.shjv.tdscdma.omc.common.message.activemq.PooledConnection.createSession(PooledConnection.java:149)
org.springframework.jms.core.JmsTemplate.createSession(JmsTemplate.java:771)
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:424)
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:448)


 

--
View this message in context: http://www.nabble.com/Blocks-on-the-method-MutexTransport.oneaway-t1634151.html#a4425949
Sent from the ActiveMQ - User forum at Nabble.com.


Re: Blocks on the method MutexTransport.oneaway

Posted by Adrian Co <ac...@exist.com>.
Hi,

There's a lot of fixes since rc2, maybe you could try the latest snapshot to
see if it has been addressed. :)

regards,
Adrian


Grant H wrote:
> 
> Phenomenon 1
> 
> When using mq4.0-rc2 version to send messages, the following problems will
> occur.
> The thread sent by messages stays on the method of CountDownLatch.await,
> which results in unsuccessful sending of following messages. And it blocks
> on the method of MutexTransport.oneaway, which waits for the previous
> successful sending message.
> 
> Name: RMI TCP Connection(4)-192.168.167.2
> State: WAITING on
> edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch@1e6978d
> Total blocked: 1  Total waited: 1
> 
> Stack trace: 
> java.lang.Object.wait(Native Method)
> java.lang.Object.wait(Object.java:474)
> edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:179)
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:73)
> org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:356)
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:63)
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:68)
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1108)
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1196)
> org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:252)
> org.apache.activemq.pool.SessionPool.createSession(SessionPool.java:116)
> org.apache.activemq.pool.SessionPool.makeObject(SessionPool.java:84)
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
> org.apache.activemq.pool.SessionPool.borrowSession(SessionPool.java:59)
> com.shjv.tdscdma.omc.common.message.activemq.PooledConnection$CustomConnectionPool.createSession(PooledConnection.java:217)
> com.shjv.tdscdma.omc.common.message.activemq.PooledConnection.createSession(PooledConnection.java:149)
> org.springframework.jms.core.JmsTemplate.createSession(JmsTemplate.java:771)
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:424)
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:448)
> 
> 
>  
> 
> 
--
View this message in context: http://www.nabble.com/Blocks+on+the+method+MutexTransport.oneaway-t1634151.html#a4500703
Sent from the ActiveMQ - User forum at Nabble.com.