-
Bug
-
Resolution: Done
-
Blocker
-
None
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
- clones
-
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"
- Closed