Hi Gary,
Changing the client broker URL to use tcp protocol fixed the issue. This
looks like the following.
tcp://1.2.3.4:61618
Thanks again for your help!
-Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-NIO-protocol-tp3540710p3545810.html
Sent f
Ah I see. I will give the new client broker URL later today.
In terms of the transportConnector we are using a specific IP address. I
just replaced it with Xs in this post for security reasons.
Thanks again!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-N
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 th
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.n
It looks correct, only change would be to just change the port on the
client broker url, so use
tcp://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61618
There is nothing particular to nio on the client, by default it picks
up the tcp impl, but there may be an issue here.
On 21 May 2011 15:48, h
