0 Replies Latest reply on Sep 4, 2015 10:50 AM by Leonard De Baets

    Creating Remote JMS Queues/Topics

    Leonard De Baets Newbie

      I'm trying to create JMS queues and topics for remote access in a clustered HA environment with Docker containers for deployment of the applications.

      Topics and queues were created for local access, InVM, but never for Remote.  I'm doing this for testing connectivity to queues and topics using the HellowWorldJMS quickstart, which works fine on my local laptop environment running Wildfly8.

      When I try to create a queue for example, using the following cli docker command (which has the jboss cli command jms-queue embedded) I get the following:

       

      docker run --rm -e DC_PORT_9990_TCP_ADDR=xxx.xx.x.x docker.cenx.localnet:5000/wildfly-cli --command="jms-queue --profile=full-ha add --queue-address=testQueue101 --entries=queue/testQueue101, java:jboss/exported/jms/queue/testQueue101"

      JBAS010839: Operation failed or was rolled back on all servers.

       

      In the Wildfly server log file, I see the following logs:

      2015-09-04 14:26:18,360 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 253) HQ221003: trying to deploy queue jms.queue.testQueue101

      2015-09-04 14:26:18,363 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 253) JBAS011601: Bound messaging object to jndi name queue/testQueue101

      2015-09-04 14:26:18,597 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 253) JBAS011605: Unbound messaging object to jndi name java:/queue/testQueue101

       

      Can anyone tell me anything about what may be the problem?  I can't understand the last two server logs, why the messaging object gets Bound to the JNDI name for the queue, and then gets unbound right after with no indication of why.