]
Miroslav Novak updated WFLY-7540:
---------------------------------
Labels: user_experience (was: )
Not possible to lookup exported JMS resources by full JNDI name with
java:jboss/exported/... prefix
----------------------------------------------------------------------------------------------------
Key: WFLY-7540
URL:
https://issues.jboss.org/browse/WFLY-7540
Project: WildFly
Issue Type: Enhancement
Components: Remoting
Affects Versions: 10.1.0.Final
Reporter: Miroslav Novak
Assignee: David Lloyd
Labels: user_experience
If exported queue/topic or connection factory is looked up from JNDI by remote client
then client must use relative JNDI name.
For example if queue is registrered in JNDI under name
{{java:jboss/exported/jms/queue/InQueue}} then client must lookup {{jms/queue/InQueue}}
In case client tries to lookup queue by full JNDI name
{{java:jboss/exported/jms/queue/InQueue}} then lookup fails with exception: {code}
javax.naming.NameNotFoundException: jboss/exported/jms/queue/InQueue -- service
jboss.naming.context.java.jboss.exported.jboss.exported.jms.queue.InQueue
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
~[na:na]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) ~[na:na]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) ~[na:na]
at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)
~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final]
at
org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)
~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
~[na:1.8.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_51]
{code}