Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.56.0
-
None
Description
We fire the ExceptionListener when a consumer is remotely-closed that has a MessageListener, since the lack of new messages arriving to produce activity could mean the application then never interacts with with the consumer object and discover the closure. The same should occur (thought it already did..) when a Session is remotely-closed whilst having a consumer with MessageListener, as the application may similarly then not interact with the session/consumer objects and discover the closure due to lack of message delivery activity.