You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by happyAMQ <jb...@olf.com> on 2009/01/29 00:28:51 UTC
Using the NIO transport causes issues
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(JMSExceptionSupport.java:62)
[java] at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1255)
[java] at
org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1339)
[java] at
org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:488)
[java] at EchoServerMT.run(EchoServerMT.java:206)
[java] at java.lang.Thread.run(Thread.java:619)
--
View this message in context: http://www.nabble.com/Using-the-NIO-transport-causes-issues-tp21717611p21717611.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Using the NIO transport causes issues
Posted by Rob Davies <ra...@gmail.com>.
You're using tcp:// on the client side though ???
On 29 Jan 2009, at 12:35, Ricardo Clemente wrote:
> I don't know why, but I'm experiencing the same problem.
>
> I'm running on a Linux (Ubuntu) the 5.2.0 version.
>
> regards,
> Ricardo
>
> On Thu, Jan 29, 2009 at 9:10 AM, Rob Davies <ra...@gmail.com>
> wrote:
>>
>> On 28 Jan 2009, at 23:28, 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(JMSExceptionSupport.java:
>>> 62)
>>> [java] at
>>>
>>> org
>>> .apache
>>> .activemq
>>> .ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1255)
>>> [java] at
>>>
>>> org
>>> .apache
>>> .activemq
>>> .ActiveMQConnection
>>> .ensureConnectionInfoSent(ActiveMQConnection.java:1339)
>>> [java] at
>>> org
>>> .apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:
>>> 488)
>>> [java] at EchoServerMT.run(EchoServerMT.java:206)
>>> [java] at java.lang.Thread.run(Thread.java:619)
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-the-NIO-transport-causes-issues-tp21717611p21717611.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>
>> Can you let us know the version of ActiveMQ and the platform - a
>> lot of
>> issues are platform specific (I get no error running on a Mac for
>> example)?
>>
>>
>> cheers,
>>
>> Rob
>>
>> Rob Davies
>> http://fusesource.com
>> http://rajdavies.blogspot.com/
>>
>>
>>
>>
>>
>>
>>
Re: Using the NIO transport causes issues
Posted by Ricardo Clemente <ri...@gmail.com>.
I don't know why, but I'm experiencing the same problem.
I'm running on a Linux (Ubuntu) the 5.2.0 version.
regards,
Ricardo
On Thu, Jan 29, 2009 at 9:10 AM, Rob Davies <ra...@gmail.com> wrote:
>
> On 28 Jan 2009, at 23:28, 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(JMSExceptionSupport.java:62)
>> [java] at
>>
>> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1255)
>> [java] at
>>
>> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1339)
>> [java] at
>> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:488)
>> [java] at EchoServerMT.run(EchoServerMT.java:206)
>> [java] at java.lang.Thread.run(Thread.java:619)
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Using-the-NIO-transport-causes-issues-tp21717611p21717611.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
> Can you let us know the version of ActiveMQ and the platform - a lot of
> issues are platform specific (I get no error running on a Mac for example)?
>
>
> cheers,
>
> Rob
>
> Rob Davies
> http://fusesource.com
> http://rajdavies.blogspot.com/
>
>
>
>
>
>
>
Re: Using the NIO transport causes issues
Posted by Rob Davies <ra...@gmail.com>.
On 28 Jan 2009, at 23:28, 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(JMSExceptionSupport.java:62)
> [java] at
> org
> .apache
> .activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:
> 1255)
> [java] at
> org
> .apache
> .activemq
> .ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:
> 1339)
> [java] at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:
> 488)
> [java] at EchoServerMT.run(EchoServerMT.java:206)
> [java] at java.lang.Thread.run(Thread.java:619)
>
> --
> View this message in context: http://www.nabble.com/Using-the-NIO-transport-causes-issues-tp21717611p21717611.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Can you let us know the version of ActiveMQ and the platform - a lot
of issues are platform specific (I get no error running on a Mac for
example)?
cheers,
Rob
Rob Davies
http://fusesource.com
http://rajdavies.blogspot.com/
Re: Using the NIO transport causes issues
Posted by happyAMQ <jb...@olf.com>.
Hi,
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:///xxx.xxx.xxx.124:3685. Reason: java.nio.channels.CancelledKeyException
java.nio.channels.CancelledKeyException
Thanks,
Jason
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(JMSExceptionSupport.java:62)
> [java] at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1255)
> [java] at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1339)
> [java] at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:488)
> [java] at EchoServerMT.run(EchoServerMT.java:206)
> [java] at java.lang.Thread.run(Thread.java:619)
>
>
--
View this message in context: http://www.nabble.com/Using-the-NIO-transport-causes-issues-tp21717611p21728273.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.