Yes, a JmsConnectionRemotelyClosedException, or something with a ProviderConnectionRemotelyClosedException based cause, is indicates the connection is done for, that the client received a connection close frame for some reason and that it wasnt expected (i.e it wasnt expecting it as response to a requested closure). Similarly a JmsConnectionFailedException, or something with ProviderFailedException based cause, can indicate other connection-breaking issues such as the connection dropping or some failure in its processing where a close frame wasnt necessarily received.
On Fri, 12 Mar 2021 at 16:57, akabhishek1 <[email protected]> wrote: > > Hi Robbie, > > Thanks a lot for quick reply. > > Can i assume that JMS Connection will be closed for > "JmsConnectionRemotelyClosedException" or > "ProviderConnectionRemotelyClosedException" exception. > > So whenever I got "JmsConnectionRemotelyClosedException" or > "ProviderConnectionRemotelyClosedException" on "onException()" method then > I will recreate JMS connection. > > Please let me know if there are any other JMS connection closed Exception > classes, so i will handle them as well. > > Could you please confirm on this or correct me if I am wrong? > > > Regards, > Abhishek Kumar > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
