WildFly HornetQ-Based Messaging Subsystem Configuration Reference: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
==<jmx-management-enabled>== | ==<jmx-management-enabled>== | ||
Can be used to turn on advanced JMX monitoring, and define the JMX domain for standby nodes. | |||
<hornetq-server> | <hornetq-server> | ||
... | ... | ||
<jmx-management-enabled>true</jmx-management-enabled> | <jmx-management-enabled>true</jmx-management-enabled> | ||
<jmx-domain>org.hornetq.standby</jmx-domain> | |||
... | ... | ||
Revision as of 20:39, 5 September 2017
Internal
<hornetq-server>
<jmx-management-enabled>
Can be used to turn on advanced JMX monitoring, and define the JMX domain for standby nodes.
<hornetq-server> ... <jmx-management-enabled>true</jmx-management-enabled> <jmx-domain>org.hornetq.standby</jmx-domain> ...
<address-settings>
<address-setting>
<redistribution-delay>
Defines how long to wait, in milliseconds, after the last consumer is closed on a queue before redistributing any messages in the queue. The default is -1, which means "disabled", which means messages won't be redistributed among clustered node peers, even if there are no consumers.