javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue!!
by Elson Vaz
Hello,
I need your support, please.
I am trying to send data through a producer in java (standalone), to broker
active mq artemis on wildfly.
error message.
javax.naming.NameNotFoundException: jms/queue -- service
jboss.naming.context.java.jboss.exported.jms.queue
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:185)
at
org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:106)
at
org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at
org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:975)
at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at
org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Wildfly configuration.(standalone-full.xml)
<jms-queue name="DGTR" entries="java:/jboss/exported/jms/queue/DGTR"/>
configration in java standalone aplication.
public final static String
JMS_CONNECTION_FACTORY_JNDI="jms/RemoteConnectionFactory";
public final static String JMS_QUEUE_JNDI="jms/queue/DGTR";
thks
4 years, 4 months
WildFly 20.0.1 Release
by Brian Stansberry
We released WildFly 20 on June 8, and next week it will be a month since
then, so it's the general time frame when we do a micro. We've got a few
fixes in the 20.x branch, one of which I know the Keycloak community is
waiting on, so I'd like to try and get a release done early next week.
Component leads, if you've got something ready to go that you think needs
to be in 20.0.1 and it isn't already in the 20.x branch, please let me know
ASAP. Generally what we put in a micro should be limited to critical
fixes, safe component upgrades that resolve CVEs or other security issues,
or less critical but very safe things where there's current community
demand.
Anything going in 20.0.1 will require a PR against the 20.x branch. (And,
of course, master.)
Best regards,
Brian
4 years, 4 months
