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

Posted to issues@activemq.apache.org by "Ivo Studensky (JIRA)" <ji...@apache.org> on 2015/10/22 14:27:28 UTC

[jira] [Updated] (ARTEMIS-274) Make ActiveMQThreadFactory instantiation running within doPrivileged block

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

Ivo Studensky updated ARTEMIS-274:
----------------------------------
    Fix Version/s: 1.2.0

> Make ActiveMQThreadFactory instantiation running within doPrivileged block
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-274
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-274
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Ivo Studensky
>             Fix For: 1.2.0, 1.1.1
>
>
> At the moment, ActiveMQThreadFactory caches AccessControlContext inside of its constructor and uses it later in newThread() method invocation to create a thread inside of doPrivileged block. This leads to not enough permissions issue when a client is trying to create a new connection on a factory taken from JNDI, see https://issues.jboss.org/browse/WFLY-5166.
> To fix it all the invocations of the factory constructor should run within a privileged block to get a privileged ACC to the factory. This change should be similar to how it works in WildFly right now. 



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