Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8705

JNDI lookup for name prefixed with "java:/" fails

XMLWordPrintable

    • Regression
    • Hide 
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/

groovy -DEAP_VERSION=7.1.0.DR12 PrepareServers7.groovy

export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/

mvn clean install -Deap=7x -Dtest=JNDILookupTestCase#lookupWithPrefixedJava | tee log.txt
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_VERSION=7.1.0.DR12 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean install -Deap=7x -Dtest=JNDILookupTestCase#lookupWithPrefixedJava | tee log.txt

      This is regression against EAP 7.0.z.

      Customer impact: This might have been used by customers with EAP 7.0. Customers have to change their application code and remove java:/ prefix from JNDI names to be able to do JNDI lookup in EAP 7.1.

      JNDI lookup for destinations prefixed with java:/ fails with following error:

      javax.naming.NameNotFoundException: "java:/jms" -- service jboss.naming.context.java.jboss.exported.java:/jms
	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
	at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:171)
	at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:92)
	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:817)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
      In more detail

      Let's have jms queue defined as follows:

      <jms-queue name="testQueue" entries="jms/queue/testQueue java:jboss/exported/jms/queue/testQueue"/>

      Initial context properties

      java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.provider.url=http-remoting://127.0.0.1:8080

      Following JNDI lookup fails with error mentioned above

      ctx.lookup("java:/jms/queue/testQueue");

            jmesnil1@redhat.com Jeff Mesnil
            mstyk_jira Martin Styk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: