<broker xmlns="http://activemq.apache.org/schema/core"; advisorySupport="true"
brokerName="etp_server"
persistent="true" >
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" />
<policyEntry queue=">"
producerFlowControl="false"
optimizedDispatch="true"/>
<policyEntry topic=">">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
<managementContext>
<managementContext createConnector="true" connectorPort="1099"/>
</managementContext>
<persistenceAdapter>
<kahaDB directory="/cache"/>
</persistenceAdapter>
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="10 gb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="20 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="20 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<transportConnectors>
<transportConnector name="openwire"
uri="tcp://0.0.0.0:61616" />
</transportConnectors>
</broker>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplex-networkConnector-can-not-reconnect-when-network-is-restored-on-ActiveMQ-5-9-tp4678187p4678286.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
