[
https://issues.apache.org/jira/browse/AMQ-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157160#comment-16157160
]
ASF subversion and git services commented on AMQ-6787:
------------------------------------------------------
Commit 035baf1722f79022c8af0a17158b2c418fa8c577 in activemq's branch
refs/heads/activemq-5.15.x from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=035baf1 ]
[AMQ-6787] release securty context on failure to addConnection subsequent to
auth, resolve leak. fix and test
(cherry picked from commit a15626193c8d3c099b0bcf1e605b892b533a4d3e)
> 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)
