WildFly ActiveMQ Destination Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 18: Line 18:


"entries" represents a square-bracked enclosed list with multiple JNDI names separated by a single space space. These names can be used by clients to look up the queue.
"entries" represents a square-bracked enclosed list with multiple JNDI names separated by a single space space. These names can be used by clients to look up the queue.
The command results in the following entry:
<pre>
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
    <server name="default">
        ...
        <jms-queue name="novaordis" entries="queue/novaordis jms/queue/novaordis java:jboss/exported/jms/queue/novaordis"/>
        ...
    </server>
</subsystem>
</pre>


=Querying the Configuration of a JMS Destination=
=Querying the Configuration of a JMS Destination=

Revision as of 20:33, 22 January 2017

Internal

Adding a Queue with CLI

jms-queue add --queue-address=novaordis --entries=[queue/novaordis jms/queue/novaordis java:jboss/exported/jms/queue/novaordis]

where:

queue-address

Represents the queue's routing configuration.

entries

"entries" represents a square-bracked enclosed list with multiple JNDI names separated by a single space space. These names can be used by clients to look up the queue.

The command results in the following entry:

<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
    <server name="default">
        ...
        <jms-queue name="novaordis" entries="queue/novaordis jms/queue/novaordis java:jboss/exported/jms/queue/novaordis"/>
        ...
    </server>
</subsystem>

Querying the Configuration of a JMS Destination

jms-queue read-resource --queue-address=myQueue