Hi You might have to decrease the soTimeout to "detect" quickly the connection is down.
Are you using "default" transportConnector configuration ? Regards JB On Wed, Jul 23, 2025 at 4:50 AM Bijju Patel <bpatel0...@gmail.com> wrote: > > Hello, > I am seeing an issue (or maybe my understanding is not clear) with the > failover protocol in ActiveMQ Classic case. > So, appreciate your thoughts and comments and if you have overcome such > cases. > > Here is the scenario and cases. Please bear with my lengthy info as I want > to be clear. > > I have an AMQ client which is connecting to a broker using failover > protocol with A:B:C brokers. > If the broker service goes down on A, the client switches to B quickly. > There is no issue here. > Also, I do see that tranportInterrupted() from TransportListener gets > called. So, everything is good. > > But, when the network is interrupted between the client and server A, the > client is not switching to B > immediately as in the above case. I see that socket connections to broker A > linger on for long time > either in SYN_SENT or FIN_WAIT_2 states. This is the only thing I noticed. > I have multiple topics > defined in client and AMQ traffic is heavy. So, the client application is > not working as intended. > Is this the correct client behavior when the network is interrupted between > client and A? > If so, is there anything in terms of the settings etc, I can do so that it > behaves similar to the above case > where the switch happens immediately when the broker service on A goes down > ? > > I am using the Classic ActiveMQ 6.1.6 version. > > Appreciate any comments or thoughts. > > Thanks, > Bijju Patel. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
