[jira] [Work logged] (ARTEMIS-2171) ThreadPoolExecutor leak under SM due to lack of privileged block

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2171?focusedWorklogId=189562&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189562 ]

ASF GitHub Bot logged work on ARTEMIS-2171:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Jan/19 17:08
            Start Date: 24/Jan/19 17:08
    Worklog Time Spent: 10m 
      Work Description: ehsavoie commented on pull request #2517: [ARTEMIS-2171]: ThreadPoolExecutor leak under SM due to lack of privileged block.
URL: https://github.com/apache/activemq-artemis/pull/2517
 
 
   * Ensuring that all threadPoolFactories are created under a privileged
   block so the threads created are under the same AccessControlContext.
   
   Jira: https://issues.apache.org/jira/browse/ARTEMIS-2171
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 189562)
            Time Spent: 10m
    Remaining Estimate: 0h

> ThreadPoolExecutor leak under SM due to lack of privileged block
> ----------------------------------------------------------------
>
>                 Key: ARTEMIS-2171
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2171
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.6.3
>            Reporter: Miroslav Novak
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Description cloned from https://issues.jboss.org/browse/WFLY-10380:
> Still researching the source of these leaks.
> The way the leak happens is, a java.util.concurrent.ThreadPoolExecutor is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the modifyThread RuntimePermission, and the thread pool never shuts down.
> We need to identify the points where TPEs are being constructed without controlled privileges.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)