You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2014/11/04 23:56:36 UTC
[jira] [Resolved] (QPID-6184) [Java Broker] Java Broker leaks
connections and sessions via SessionPrincipal and ConnectionPrincipal in
Thread inherited access control context
[ https://issues.apache.org/jira/browse/QPID-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-6184.
------------------------------
Resolution: Fixed
Changes look reasonable to me.
> [Java Broker] Java Broker leaks connections and sessions via SessionPrincipal and ConnectionPrincipal in Thread inherited access control context
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6184
> URL: https://issues.apache.org/jira/browse/QPID-6184
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30
> Reporter: Alex Rudyy
> Assignee: Keith Wall
> Fix For: 0.31
>
>
> On thread creation, current caller AccessControlContext is stored in Thread field inheritedAccessControlContext. If such AccessControlContext contains references to SessionPrincipal and ConnectionPrincipal instances (i.e. thread is created in Connection/Session), the corresponding Session and Connection objects are not GC'ed until Thread stops running. If Thread is created in implementation of java.util.concurrent. Executor it can be re-used and remain alive until Executor utilizes the thread. Potentially, such threads might stay alive until Broker JVM is shutdown.
--
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