]
Emmanuel Hugonnet commented on WFLY-13949:
------------------------------------------
Then the reproducer code is 'wrong' as it never target the DLQ queue
JNDI lookup for JMS Queue failing
---------------------------------
Key: WFLY-13949
URL:
https://issues.redhat.com/browse/WFLY-13949
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 20.0.1.Final
Reporter: Francis Griffin
Assignee: Emmanuel Hugonnet
Priority: Major
Attachments: dpsrTest.tgz
I have a JMS app which has been running successfully under WF10 for some years. I'm
trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK
is OpenJDK 11.
I've tried to make the reproducible case as simple as possible. The server is
unpacked from the downloaded tar.gz, and is not modified except to add a guest user for
JMS (which is not needed for the reproducible case, since we never actually create a
Connection). The queue is the DLQ queue defined in the distribution.
The error is a NameNotFoundException:
Exception in thread "main" javax.naming.NameNotFoundException: jms/queue --
service jboss.naming.context.java.jboss.exported.jms.queue
at
org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at
org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at
org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at
org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at
org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at
org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at
org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at
org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at
org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at
org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at
org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at
org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
No matter what queue name I use, the lookup is failing on the string jms/queue rather
than the expected jms/queue/DLQ.
I fully expect that this is some stupid error on my part, something I'm looking at
and just not seeing, because I know of others (albeit using Windows) who are using
20.0.1.Final for the full app without issue. But I can't for the life of me see what
it is.
Tha actual full application looks up a ConnectionFactory of
"jms/RemoteConnectionFactory" and creates Connections and Sessions before
looking up the Queue name. The lookup for the factory name works perfectly, as does the
other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown
above.