WildFly HornetQ-Based Messaging Subsystem Configuration Reference: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
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>
     ...
     ...


==<connectors>==
{{Internal|WildFly HornetQ-Based Messaging Subsystem Configuration Reference - Connectors|<connectors>}}
==<acceptors>==
{{Internal|WildFly HornetQ-Based Messaging Subsystem Configuration Reference - Acceptors|<acceptors>}}


==<address-settings>==
==<address-settings>==

Latest revision as of 17:39, 26 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>
   ...

<connectors>

<connectors>

<acceptors>

<acceptors>

<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.