[CONF] Apache ActiveMQ > Configuring Transports

[Gary Tully (Confluence)]

Title: Message Title

There's 1 new edit on this page

Configuring Transports Gary Tully edited this page Here's the version comment Gary Tully edited at 09:36 AM obsolete enableStatusMonitor Here's what changed: ... property name default description allowLinkStealing false This is enabled for default for MQTT transport. Link Stealing is where the last of two or more connections with the same id (clientID for JMS) is deemed the valid connection and the older one is closed by the broker. discoveryURI null If set, the multicast discovery address for client connections to find the broker. enableStatusMonitor falseWill monitor connections to determine if they are blocked. Obsolete - replaced with the InactivityMonitor functionality name null The name of the TransportConnector instance. rebalanceClusterClients false Will automatically re-balance clients across the cluster on changes of topology. updateClusterClients false If enabled, will update client connections (if they use the failover:// transport) of changes to the broker cluster. updateClusterClientsOnRemove false Will update clients if a broker is removed from the cluster. updateClusterFilter null Comma separated list of regular expressions. Brokers with a name matching the pattern will be included for client updates. uri null The bind address for the transport. warnOnRemoteClose false If set, issue a WARN log event if a client closes its connection in an abrupt manner, one example being a load-balancer health check. For a regular JMS client this WARN message is indicative of a client going away without a connection.close (5.16) ... Code Block language xml <broker>    <!-- ... -->    <transportConnectors>      <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" enableStatusMonitor="true"/>    </<transportConnectors>    <!-- ... --> </broker> ... Go to page history View page

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 6.9.0