Hey,
I saw some configurations in ActiveMQConnectionFactory and FailoverTransport like "initialReconnectDelay" "backOffMultiplier" "maxReconnectAttempts" "useExponentialBackOff". If we cannot stop client in above case than atleast we can create delay after each reconnect. I found that if a client is not able to connect to the broker (may be broker is not runnning), it keep on retrying with exponential backoff and respect the configuration. But in case of exception there is nothing like backoff period or maxreconnect attempts. It can be resolved if FailoverTransport do the same things like reconnectdelay and exponentialBackOff while throwing the exception. Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-consumer-not-getting-removed-tp4678812p4679169.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
