[jboss-jira] [JBoss JIRA] (WFLY-12477) CommandDispatcher commands cannot read application jndi namespace

[Paul Ferraro (Jira)]

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

Paul Ferraro updated WFLY-12477:
--------------------------------
    Description: 
A command containing the following code:
{noformat}
public class MyCommand implements Command<Void, Void> {
    public Void execute(Void context) throws Exception {
        new InitialContext().lookup("java:comp/env/existing-resource");
    }
}
{noformat}

currently throws a NameNotFoundException, even though the same JNDI lookup succeeds on the caller that invoked the command.
A command executed with the command dispatcher should be able to perform JNDI lookup from the local application namespace.

In fact, the following application callbacks from the clustering API are unable to read from the application's JNDI namespace:

* CommandDispatcher command execution
* CommandDispatcherFactory cluster membership listener
* Cache topology membership listener
* Registry listener
* ServiceProviderRegistry listener

  was:
A command containing the following code:
{noformat}
public class MyCommand implements Command<Void, Void> {
    public Void execute(Void context) throws Exception {
        new InitialContext().lookup("java:comp/env/existing-resource");
    }
}
{noformat}

currently throws a NameNotFoundException, even though the same JNDI lookup succeeds on the caller that invoked the command.
A command executed with the command dispatcher should be able to perform JNDI lookup from the local application namespace.

In fact, the following application callbacks from the clustering API are unable to read from the application's JNDI namespace:

* CommandDispatcher command execution
* CommandDispatcherFactory cluster membership listener
* Cache topology membership listener
* Registry listener
* ServiceProviderRegistry listener
* Singleton election policy and listener



> CommandDispatcher commands cannot read application jndi namespace
> -----------------------------------------------------------------
>
>                 Key: WFLY-12477
>                 URL: https://issues.jboss.org/browse/WFLY-12477
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 17.0.1.Final
>            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 {
>         new InitialContext().lookup("java:comp/env/existing-resource");
>     }
> }
> {noformat}
> currently throws a NameNotFoundException, even though the same JNDI lookup succeeds on the caller that invoked the command.
> A command executed with the command dispatcher should be able to perform JNDI lookup from the local application namespace.
> In fact, the following application callbacks from the clustering API are unable to read from the application's JNDI namespace:
> * 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)