[
https://issues.apache.org/jira/browse/QPIDJMS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839146#comment-17839146
]
ASF subversion and git services commented on QPIDJMS-600:
---------------------------------------------------------
Commit 90eb60f59cb59b7b9ad8363ee8a843d6903b8e77 in qpid-jms's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=90eb60f5 ]
QPIDJMS-600 Ensure session and connection close await async sends
Session and Connection close should be awaiting the outcome of async send
completions before returning. This change allows them to await up to the
close timeout value before moving on and failing any completions that are
not completed after that point. Several tests added to cover this behavior.
> Session and Connection close should await async send completion
> ---------------------------------------------------------------
>
> Key: QPIDJMS-600
> URL: https://issues.apache.org/jira/browse/QPIDJMS-600
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 2.5.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: 2.6.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
