Re: Failover Transport hangs forever on connection.start() in Master/Slave

Hi, Following is the stack trace for successful connection to activeMQ: # 2019-04-30 20:51:52 DEBUG TaskRunnerFactory:91 - Initialized TaskRunnerFactory[ActiveMQ Task] using ExecutorService: java.util.concurrent.ThreadPoolExecutor@6504e3b2[Running, pool siz

Re: Failover Transport hangs forever on connection.start() in Master/Slave

Can you upload the full stack dump from the client application when this happens as a GIST on github.com and send the link? It's OK to filter out any proprietary bits as long as all of the threads that have ActiveMQ in the call history are listed. BTW, the "oneWay" method sends a message over the

Re: Failover Transport hangs forever on connection.start() in Master/Slave

I am using activemq version 5.15.8. I see the issue when client first time tries to connect to activemq broker and if the randomly picked broker url happens to be slave, the call is stuck forever in FailoverTransport class at the following point: ## @Override publ

Re: Failover Transport hangs forever on connection.start() in Master/Slave

You haven't mentioned a version of your activemq, there were some issues with that in older versions... We're on 5.6.0 and above - no issues... See http://activemq.apache.org/failover-transport-reference -- Sent from: http://activemq.

Failover Transport hangs forever on connection.start() in Master/Slave

Hi,  I have Master/Slave broker url for failover transport as follows:  (ssl://brokerurl1:61616,ssl://brokerurl2:61616)?timeout=5000&startupMaxReconnectAttempts=5&maxReconnectAttempts=5   Client picks up one broker url at random, if the url picked up to connect at random is slave, the call hangs