activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-5417) Use correct classloader in TaskRunnerFactory
Date Wed, 29 Oct 2014 10:36:33 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac resolved AMQ-5417.
--------------------------------
    Resolution: Fixed

Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/dffccb1c

> 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)

Mime
View raw message