[
https://issues.jboss.org/browse/WFLY-8356?page=com.atlassian.jira.plugin....
]
Stuart Douglas moved JBEAP-9536 to WFLY-8356:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8356 (was: JBEAP-9536)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
Naming
(was: JMS)
(was: Naming)
Affects Version/s: (was: 7.1.0.DR12)
(was: 7.1.0.DR13)
Affects Testing: (was: Regression,Blocks Testing)
(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"
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-8356
URL:
https://issues.jboss.org/browse/WFLY-8356
Project: WildFly
Issue Type: Bug
Components: JMS, Naming
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Priority: Blocker
Labels: eap71_alpha
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:
{code}
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
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)