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

Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/09/07 16:25:00 UTC

[jira] [Updated] (AMQ-6787) Memory leak - JaasAuthenticationBroker retaining instances of JaasAuthenticationBroker$JaasSecurityContext for connections that fail with InvalidClientIDException

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

Timothy Bish updated AMQ-6787:
------------------------------
    Fix Version/s: 5.15.1

> Memory leak - JaasAuthenticationBroker retaining instances of JaasAuthenticationBroker$JaasSecurityContext for connections that fail with InvalidClientIDException 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6787
>                 URL: https://issues.apache.org/jira/browse/AMQ-6787
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.15.1, 5.16.0
>
>
> If a client can authenticate but subsequently fails to add a connection due to InvalidClientIDException - clientId already in use for example. The security context is retained by the JaasAuthenticationBroker in error.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)