Remote session closure, coupled with ongoing client activity, is inherently a bit of a race. You may perform a new operation which itself has to fail, because the resource is now/being closed. You are going to get an exception through the Exception Listener, because its generally an unexpected event (though seemingly not for ServiceBus), and there may be no other way to know there is an issue with the session or connection if you dont actively use them. You also have message listeners, consumers which will specifically never ever find out about such a problem otherwise unless that is done, because they do no operations until future messages arrive, which they never will as a result of the unexpected remote closure.
In order to reproduce the reaction to a server remotely closing the session, you would need a test server that remotely closes the session. On Thu, 4 Feb 2021 at 23:56, akabhishek1 <[email protected]> wrote: > > Hi Team, > > We recently upgraded Qpid library to "qpid-jms-client-0.56.0" and started > getting ProviderException with session closed error while communicating with > ServiceBus broker. > > We are trying to reproduce ProviderException with closed session. > > Scenario : > 1. Publish message > 2. Got illegalStateException - The MessageProducer is closed/The > MessageProducer was closed due to an unrecoverable error. > 3. ResetPoducer -- (Assuming session is not closed) --> Which throws "The > Session was closed due to an unrecoverable error." > 4. ProviderException -- "Unknown error from remote peer" --> why are we > getting this exception as well in error call stack? > > Please find attached "ProviderException_SessionClosed_Qpid.json" and > SessionClosed_ProviderException.PNG. > > We are cleared upto ResetPoducer issue but not cleared with > ProviderException. > > If you check attached stack trace there is no directly link between > IllegalStateException and ProviderException. > > We have fixed ResetPoducer but not able to fix ProviderException issue, > because we are not able to generate this issue. > > Could you please check attached stack trace and help with below queris - > 1. Is ProviderException being generated by > "org.apache.qpid.jms.JmsSession.checkClosed" ? Please refer error > Array[1]-parsedStack[0] > 2. How can we generate ProviderException while creating destination ? Please > refer error Array[1]-parsedStack[1] > > Could you please let us know your thought, it will help us to close this > issue. Let me know for any query. > > ProviderException_SessionClosed_Qpid.json > <http://qpid.2158936.n2.nabble.com/file/t396358/ProviderException_SessionClosed_Qpid.json> > > SessionClosed_ProviderException.PNG > <http://qpid.2158936.n2.nabble.com/file/t396358/SessionClosed_ProviderException.PNG> > > > 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]
