Looking into your stack traces, I dont see how it is possible for the situation to occur as described.
The final exception with stacktrace as shown, was only created after a point at which the handling leading to its creation has rendered it impossible for the getClientID() method to be called without throwing. The failure cause was atomically set before the exception indicated was created, and this would ensure that calling getClientID subsequently throws. The stack of the exception itself reinforces this as it spans the point where it occurs. I think you must be seeing cross-connection object interaction somehow. Ensure that your ExceptionListener can only operate on the connection object it is being set on. On Tue, 9 Mar 2021 at 14:04, akabhishek1 <[email protected]> wrote: > > Hi Robbie, > > I would like to provide you one more input. We got 'Unknown error from > remote peer' error today morning due to > JmsConnectionRemotelyClosedException. > In first scenario connection was active and in second scenario connection > was active. I compared both stacktrace and both are similar. > > Expected behaviour - As we got “JmsConnectionRemotelyClosedException”, then > in both scenario connection should be inactive. Please correct me if I am > wrong. > > Please find below exception details - > > First Exception - > Connection exception from 'servicebusConnector_2', isConnectionActive > 'false', Reason 'Unknown error from remote peer' > Refer here for Stacktrace - > https://github.com/abhikt48/servicebus/blob/master/9_march_2021/ConnectionRemoteClose_isConnectionActive_False.txt > > Second Exception - > Connection exception from 'servicebusConnector_2', isConnectionActive > 'true', Reason 'Unknown error from remote peer' > Refer here for Stacktrace - > https://github.com/abhikt48/servicebus/blob/master/9_march_2021/ConnectionRemoteClose_isConnectionActive_True.txt > > Please suggest your opinion. > > 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]
