activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Problem with NIO protocol
Date Mon, 23 May 2011 15:24:51 GMT
no, that is my point, there is nothing nio specific on the client. The
nio implementation is server side only in activemq 5.x
so clients should still use the tcp scheme for the brokerURL. The nio
scheme is just for the the transportConnector in the broker xml
configuration.

One other thought is that the broker host is multi homed, so you may
need the wildcard address 0.0.0.0:port or a specific available IP
address in the transportConnector

On 23 May 2011 15:56, hodgesz <hodgesz@gmail.com> wrote:
> Hi Gary,
>
> Thanks for your response.
>
> Don't you mean the client should use
> nio://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61618 which is what I have
> tested that causes the error?  Your client example uses tcp as the protocol.
>
> -Jonathan
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-NIO-protocol-tp3540710p3544317.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
http://fusesource.com
http://blog.garytully.com

Mime
View raw message