WildFly ActiveMQ Destination Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
</server> | </server> | ||
</subsystem> | </subsystem> | ||
</pre> | |||
The equivalent configuration for a topic: | |||
<pre> | |||
<jms-topic name="playground-topic" | |||
entries="topic/playground-topic jms/topic/playground-topic java:jboss/exported/jms/topic/playground-topic"/> | |||
</pre> | </pre> | ||
Latest revision as of 18:49, 29 March 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>
The equivalent configuration for a topic:
<jms-topic name="playground-topic"
entries="topic/playground-topic jms/topic/playground-topic java:jboss/exported/jms/topic/playground-topic"/>
Querying the Configuration of a JMS Destination
jms-queue read-resource --queue-address=myQueue