[jboss-jira] [JBoss JIRA] (WFLY-6008) CommandDispatcher commands execute using wrong TCCL

Paul Ferraro (Jira) issues at jboss.org
Fri Sep 6 15:34:00 EDT 2019


     [ https://issues.jboss.org/browse/WFLY-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-6008:
-------------------------------
    Git Pull Request: https://github.com/wildfly/wildfly/pull/12602  (was: https://github.com/wildfly/wildfly/pull/12597)


> CommandDispatcher commands execute using wrong TCCL
> ---------------------------------------------------
>
>                 Key: WFLY-6008
>                 URL: https://issues.jboss.org/browse/WFLY-6008
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.CR5
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Major
>
> A command containing the following code:
> {noformat}
> public class MyCommand implements Command<Void, Void> {
>     public Void execute(Void context) throws Exception {
>         Thread.currentThread().getClassLoader().loadClass(this.getClass().getName());
>     }
> }
> {noformat}
> currently throws a ClassNotFoundException.
> A command executed with the command dispatcher should be able to load application classes using the TCCL.
> In fact, the following application callbacks from the clustering API all use the wrong TCCL:
> * CommandDispatcher command execution
> * CommandDispatcherFactory cluster membership listener
> * Cache topology membership listener
> * Registry listener
> * ServiceProviderRegistry listener



--
This message was sent by Atlassian Jira
(v7.13.5#713005)


More information about the jboss-jira mailing list