That helped a lot - the version number of the NMS client library would be
helpful here too.

Looking at the code, it appears the error is caused by an unconnected
socket, which means either (a) the socket never connected (more code digging
needed to see how feasible this is), or (b) the socket connected and
disconnected quickly.

Are there any messages logged on the broker?  Does this happen every time?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Can-not-Connect-to-ActiveMQ-The-operation-is-not-allowed-on-non-connected-sockets-tp4684696p4684746.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to