Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12477

CommandDispatcher commands cannot read application jndi namespace

    XMLWordPrintable

Details

    Description

      A command containing the following code:

      public class MyCommand implements Command<Void, Void> {
          public Void execute(Void context) throws Exception {
              new InitialContext().lookup("java:comp/env/existing-resource");
          }
      }
      

      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 all unable to read from the application's JNDI namespace:

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

      Attachments

        Activity

          People

            pferraro@redhat.com Paul Ferraro
            pferraro@redhat.com Paul Ferraro
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: