muskaan62 commented on issue #2849:
URL: https://github.com/apache/activemq/issues/2849#issuecomment-6972435388

   Thanks @mattrpav We are already using ActiveMQ's Failover Transport in our 
actual application with the following configuration:
   
   `failover:(ssl://url1,ssl://url2)`
   
   However, we are still observing that when one Session encounters an 
exception or gets interrupted during an operation, the other Session sharing 
the same Connection also fails with an `InterruptedIOException`.
   
   My understanding is that Failover Transport should automatically attempt to 
reconnect by establishing a new physical transport connection when an I/O 
failure occurs, allowing the application to recover without manual connection 
recreation.
   
   We are also implementing application-level retry logic. Despite this, the 
failure in one Session appears to affect the other Session as well.
   
   Is this expected behaviour with ActiveMQ Failover Transport? Shouldn't it 
attempt to reconnect and restore the connection rather than propagating the 
`InterruptedIOException` to other Sessions?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to