[jboss-jira] [JBoss JIRA] (WFLY-8766) EJB at HTTP client fails with WFNAM00026: No provider for found for URI: ejb

Stuart Douglas (JIRA) issues at jboss.org
Sun May 14 22:16:01 EDT 2017


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

Stuart Douglas moved JBEAP-10890 to WFLY-8766:
----------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8766  (was: JBEAP-10890)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: EJB
                       Naming
                           (was: EJB)
                           (was: Naming)
    Affects Version/s:     (was: 7.1.0.DR18)


> EJB at HTTP client fails with WFNAM00026: No provider for found for URI: ejb
> -------------------------------------------------------------------------
>
>                 Key: WFLY-8766
>                 URL: https://issues.jboss.org/browse/WFLY-8766
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Naming
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>
> This is a regression between EAP 7.1.0.DR17 and DR18.
> When using HTTP transport, I started getting this exception:
> {noformat}
> 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)
> {noformat}
> 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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list