Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8914

(7.1.0.DR12) jboss-client.jar cannot be used for remote JNDI lookup - "javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 7.1.0.DR14
    • 7.1.0.DR12, 7.1.0.DR13
    • JMS, Naming
    • Regression, Blocks Testing
    • Hide

      If following dependencies are added before jboss-client.jar then lookup works - it will enable to run some of our JMS testing. This is not good workaround for customers as it negatively affects user experience:

              <dependency>
            <groupId>org.wildfly.security</groupId>
            <artifactId>wildfly-elytron</artifactId>
            <version>1.1.0.Beta25</version>
        </dependency>
        <dependency>
            <groupId>org.wildfly</groupId>
            <artifactId>wildfly-naming-client</artifactId>
            <version>1.0.0.Beta10</version>
        </dependency>

      To run attached reproducer with workaround run following command:

      java -cp ${JBOSS_HOME}/modules/system/layers/base/org/wildfly/security/elytron-private/main/wildfly-elytron-1.1.0.Beta25-redhat-1.jar:${JBOSS_HOME}/modules/system/layers/base/org/wildfly/naming-client/main/wildfly-naming-client-1.0.0.Beta10-redhat-1.jar:./jboss-client.jar:./target/jms-clients-1.0-SNAPSHOT.jar ProducerTransSession
      Show
      If following dependencies are added before jboss-client.jar then lookup works - it will enable to run some of our JMS testing. This is not good workaround for customers as it negatively affects user experience: <dependency> <groupId>org.wildfly.security</groupId> <artifactId>wildfly-elytron</artifactId> <version>1.1.0.Beta25</version> </dependency> <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-naming-client</artifactId> <version>1.0.0.Beta10</version> </dependency> To run attached reproducer with workaround run following command: java -cp ${JBOSS_HOME}/modules/system/layers/base/org/wildfly/security/elytron- private /main/wildfly-elytron-1.1.0.Beta25-redhat-1.jar:${JBOSS_HOME}/modules/system/layers/base/org/wildfly/naming-client/main/wildfly-naming-client-1.0.0.Beta10-redhat-1.jar:./jboss-client.jar:./target/jms-clients-1.0-SNAPSHOT.jar ProducerTransSession
    • Hide

      To reproduce the issue:

      • Download attached clients.zip and unzip (you need to be on redhat vpn):
        • build: mvn clean install
        • run client by: java -cp ./jboss-client.jar:target/jms-clients-1.0-SNAPSHOT.jar ProducerTransSession

      See exception in client log.

      No running server is needed to reproduce the issue but for verification that everything is working with running server do:

      • download EAP 7.1.0.DR12 and attached standalone-full-ha.xml
      • copy standalone-full-ha.xml to $JBOSS_HOME/standalone/configuration/standalone-full-ha.xml
      • start server by sh standalone.sh -c standalone-full-ha.xml
      Show
      To reproduce the issue: Download attached clients.zip and unzip (you need to be on redhat vpn): build: mvn clean install run client by: java -cp ./jboss-client.jar:target/jms-clients-1.0-SNAPSHOT.jar ProducerTransSession See exception in client log. No running server is needed to reproduce the issue but for verification that everything is working with running server do: download EAP 7.1.0.DR12 and attached standalone-full-ha.xml copy standalone-full-ha.xml to $JBOSS_HOME/standalone/configuration/standalone-full-ha.xml start server by sh standalone.sh -c standalone-full-ha.xml

      Customer impact: Customer cannot use jboss-client.jar (from 7.1.0.DR12) in its client application to perform remote JNDI lookup to server. This affects most basic JMS scenarios and is regression against EAP 7.0.0 and EAP 7.1.0.DR11.

      Exception thrown from client when performing JNDI lookup:

      javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null
	at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:488)
	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:127)
	at javax.naming.InitialContext.lookup(InitialContext.java:417)
	at ProducerTransSession.run(ProducerTransSession.java:91)
Producer got exception and ended:javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: null

        2. standalone-full-ha.xml
          35 kB
          Miroslav Novak

            sdouglas1@redhat.com Stuart Douglas
            mnovak1@redhat.com Miroslav Novak
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: