[
https://issues.apache.org/jira/browse/QPIDJMS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885442#comment-17885442
]
ASF subversion and git services commented on QPIDJMS-602:
---------------------------------------------------------
Commit 1f2cfe3775f99a263ede3b3aba4f359125835773 in qpid-jms's branch
refs/heads/1.x from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=1f2cfe37 ]
QPIDJMS-602: fix potential for session shutdown NPE during competing local and
remote closures
Make the ProviderFuture creation safe from NPE, validate a future is returned
and noop the
completion wait if not since the provider ref is gone already.
Add additional try-finally to ensure executor shutdown occurs.
(cherry picked from commit 82557f96f8da8767277db18f0aa7db7d5556a132)
> racing local and remote closures can NPE in session shutdown, cause executor
> leak
> ---------------------------------------------------------------------------------
>
> Key: QPIDJMS-602
> URL: https://issues.apache.org/jira/browse/QPIDJMS-602
> Project: Qpid JMS
> Issue Type: Bug
> Affects Versions: 1.12.0, 2.6.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.6.1, 1.12.1
>
>
> Following QPIDJMS-600, when local resource teardown (e.g due to a
> connection.close()) overlaps with similar teardown provoked by remote
> connection closure, the session shutdown attempts to await async send
> completions can NPE, causing it not to shut down the related completions
> executor, if it tries to use the underlying provider after it has gone.
--
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
