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

Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2014/10/29 11:26:34 UTC

[jira] [Created] (AMQ-5417) Use correct classloader in TaskRunnerFactory

Dejan Bosanac created AMQ-5417:
----------------------------------

             Summary: Use correct classloader in TaskRunnerFactory
                 Key: AMQ-5417
                 URL: https://issues.apache.org/jira/browse/AMQ-5417
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.10.0
            Reporter: Dejan Bosanac
            Assignee: Dejan Bosanac
             Fix For: 5.11.0


TaskRunnerFactory's default executor is initialised when the first task is executed. It's also given the ThreadFactory object, which is used to create threads for the thread pool. The issue with this is when the first task is initiated from the vm transport in osgi environment, we can have transport connector threads for other transport executed in the wrong classpath. This could lead to various problems afterwards. There needs to be a way to provide the desired classloader for those threads



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)