Thanks for ur reply Sachindra, actually we create ActiveMQConnection factory in only one place and use a pool so the connection will use that. and this error won't pop up till we run it for some longer period. Thats why we thought that it should have some connection with the bug.
Thanks for the reply and reagards Kalana Sachindra Nath wrote: > > Hi Kalana, > Check for a code/configuration that sets the client id, either on the > ActiveMQConnectionFactory or on an ActiveMQConnection. The client id > should > be unique among the connected clients (as per the JMS Spec). > > I believe the issue at the AMQ site was related to > InvalidClientIdException, > even when the previous client had closed its connection. > regards > Sachindra > -- View this message in context: http://www.nabble.com/client-already-connected-with-same-clientId-error-tp16494147s2354p16535658.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
