We have a web application which is working on Wildfly 10.1.0/Java 8. I'm trying to port it to Wildfly 13/Java 10 (Oracle Java 10.0.1).
I'm trying to create a JMS queue with a JNDI name for remote access.
Example of the command I use from jboss-cli to create the JMS queue:
jms-queue add --queue-address=larrys_queue --entries=java:/jboss/exported/queue/com.example.LarrysQueue
That appears to succeed. When I list the JMS queues with
/subsystem=messaging-activemq/server=default/jms-queue=*:read-resource
my queue is visible and seems correct:
"address" => [
("subsystem" => "messaging-activemq"),
("server" => "default"),
("jms-queue" => "larrys_queue")
],
"outcome" => "success",
"result" => {
"durable" => true,
"entries" => ["java:/jboss/exported/queue/com.example.LarrysQueue"],
"legacy-entries" => undefined,
"selector" => undefined
}
But, when I look for the JNDI name with
/subsystem=naming:jndi-view
it's not there.
"java:jboss/exported" => {"jms" => {
"class-name" => "javax.naming.Context",
"children" => {"RemoteConnectionFactory" => {
"class-name" => "org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory",
"value" => "ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=8090&host=HOSTNAME], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
}}
}},
and my application which is trying to access this remotely gets a javax.naming.NameNotFoundException.
Is this a Wildfly 13 bug?
Did something change in Wildfly 13 so I have to do this a different way?
Any troubleshooting advice?
Thanks,
Larry