Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.5.0
-
None
Description
According to the JMS specification the close of a session or connection should be allowing for messages sent via the asynchronous API to complete normally before completing the close. Currently this is not being allow to happen and pending asynchronous sends are failed from a call to session or connection close. The MessageProducer close is awaiting completion of asynchronous sends as the specification requires.
Attachments
Issue Links
- causes
-
QPIDJMS-602 racing local and remote closures can NPE in session shutdown, cause executor leak
- Closed