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

(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

Details

    • 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
    • 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

    Description

      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

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. 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"

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              sdouglas1@redhat.com Stuart Douglas
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: