Thanks for your reply. I have removed discoveryUri and i still get this exception when clients are trying to connect to ActiveMq broker. Clients get this exception on every 3-4 attempts. Is there anyway i can avoid this exception as my users use these clients to get the live updates and it is very important that they should not get connection errors.
Thanks, Surya > > no. if your not using muticast discovery you can omit the whole > discoveryUri attribute. That is only used to advertise a specific > connector. > >> <transportConnector name="default" >> uri="tcp://170.19.18.141:61616?soTimeout=10000&connectionTimeout=30000" >> discoveryUri="tcp://172.19.18.141"/> >> </transportConnectors> >> > > > -- View this message in context: http://www.nabble.com/Exception-on-client-connection-tf2669782.html#a7583482 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
