You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2016/07/29 09:20:20 UTC

[jira] [Resolved] (QPID-6377) Connection's taskpool not shutdown if Connection is closed from the broker side

     [ https://issues.apache.org/jira/browse/QPID-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lorenz Quack resolved QPID-6377.
--------------------------------
    Resolution: Fixed

merge looks good

> Connection's taskpool not shutdown if Connection is closed from the broker side
> -------------------------------------------------------------------------------
>
>                 Key: QPID-6377
>                 URL: https://issues.apache.org/jira/browse/QPID-6377
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.18, 0.22, 0.30
>            Reporter: Keith Wall
>            Assignee: Lorenz Quack
>             Fix For: qpid-java-6.1, qpid-java-6.0.5
>
>         Attachments: LeakedConnectionThreadsBefore.png
>
>
> If the client's connection is closed from the Broker side, the taskpool used to deliver unrouteable messages and some asynchronous exceptions is not shutdown.   This will cause a small memory leak and potentially leaked threads too.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org