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

EJB@HTTP client fails with WFNAM00026: No provider for found for URI: ejb

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Beta1
    • None
    • EJB, Naming
    • None

    Description

      This is a regression between EAP 7.1.0.DR17 and DR18.
      When using HTTP transport, I started getting this exception:

      Exception in thread "main" javax.naming.OperationNotSupportedException: WFNAM00026: No provider for found for URI: ejb
      	at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:490)
      	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:149)
      	at javax.naming.InitialContext.lookup(InitialContext.java:417)
      	at client.Client.main(Client.java:37)
      

      It seems that upstream tests for HTTP transport are passing, so this must somehow depend on how the dependencies are setup...?

      Reproducer at https://github.com/jmartisk/mock-artifacts/tree/17fca5083d68c3b77d277196fa753f75a8d577b2/ejbclient/eap7.1-httpclient

      when you downgrade the EJB client BOM (in client/pom.xml) from 7.1.0.Beta1-redhat-3 to 7.1.0.Beta1-redhat-2 (DR17), it will start working.

      Attachments

        Issue Links

          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: