You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/04 12:47:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16114318#comment-16114318 ]
ASF subversion and git services commented on AMQ-6787:
------------------------------------------------------
Commit a15626193c8d3c099b0bcf1e605b892b533a4d3e in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a156261 ]
[AMQ-6787] release securty context on failure to addConnection subsequent to auth, resolve leak. fix and test
> 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.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)