activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From happyAMQ <>
Subject Re: Using the NIO transport causes issues
Date Thu, 29 Jan 2009 14:47:47 GMT


Sorry, I should have given more info.  AMQ 5.2,  Linux broker,  Windows
client.  JDK 1.6.0_06.

I don't always get it,  about 1/2 the time.  Simple echo client/echo server
application.  Lots of clients and servers running.  When it happens it
leaves a bunch of "ActiveMQ Transport Initiator" threads in the broker, 
even after I shut down the peers.

I also get the following exception on the Linux broker machine:
ERROR NIOTransport                   - Could not stop service:
tcp:/// Reason: java.nio.channels.CancelledKeyException


happyAMQ wrote:
> Anyone know why I would be seeing the following exception when using the
> NIO transport connector.  I do not see this with TCP.  
>   [java] javax.jms.JMSException: Wire format negotiation timeout: peer did
> not send his wire format.
>      [java] 	at
> org.apache.activemq.util.JMSExceptionSupport.create(
>      [java] 	at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(
>      [java] 	at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(
>      [java] 	at
> org.apache.activemq.ActiveMQConnection.start(
>      [java] 	at
>      [java] 	at

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message