[jboss-jira] [JBoss JIRA] (WFLY-7540) Not possible to lookup exported JMS resources by full JNDI name with java:jboss/exported/... prefix

Miroslav Novak (JIRA) issues at jboss.org
Wed Nov 9 08:01:00 EST 2016


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

Miroslav Novak moved JBEAP-5558 to WFLY-7540:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-7540  (was: JBEAP-5558)
           Issue Type: Enhancement  (was: Bug)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Remoting
                           (was: JMS)
                           (was: Remoting)
       Target Release:   (was: 7.1.0.GA)
    Affects Version/s: 10.1.0.Final
                           (was: 7.0.0.GA)
                           (was: 7.1.0.DR2)


> 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: Jeff Mesnil
>
> 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}



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


More information about the jboss-jira mailing list