On 4/9/24 15:03, alan.masciang...@lmco.com wrote:
Greetings,
We've encountered an issue when closing JMSContext while doing async sends we
tracked down to the exception being thrown here
https://github.com/apache/qpid-jms/blob/2.5.0/qpid-jms-client/src/main/java/org/apache/qpid/jms/JmsSession.java#L373C51-L373C118.
This appears to be at odds with the how javax.jms.Session and
javax.jms.JmsContext are expected to behave. From the close() Javadoc
This method must not return until any incomplete asynchronous send operations
for this JMSContext have been completed and any CompletionListener callbacks
have returned. Incomplete sends should be allowed to complete normally unless
an error occurs.
It appears to me incomplete sends are not being allowed to be completed
normally but rather an exception is being thrown?
You are correct this should be handled by session and connection close
as is done in the MessageProducer, I've created a JIRA for this and will
look into adding handling for this:
https://issues.apache.org/jira/browse/QPIDJMS-600
--
Tim Bish
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
