![]() TransportListener directly on the ActiveMQConnectionFactory, so that Options available for handling this scenario. Under the Failover transport send operations will, by default,īlock indefinitely when the broker becomes unavailable. Try with : failover:(tcp://localhost:9125?useInactivityMonitor=true&wireFormat.maxInactivityDuration=1000& wireFormat.maxInactivityDurationInitalDelay=10&initialReconnectDelay=10&maxReconnectAttempts=0&timeout=1000,tcp://localhost:9126?useInactivityMonitor=true&wireFormat.maxInactivityDuration=1000& wireFormat.maxInactivityDurationInitalDelay=10&initialReconnectDelay=10&maxReconnectAttempts=0&timeout=1000)?randomize=true WireFormat.maxInactivityDuration=1000 means after 1s if no data has been received the broker will close the connection !!? is it a good idea ? ![]() MaxInactivityDurationInitalDelay : The initial delay before starting inactivity checks. MaxInactivityDuration : Timeout, in milliseconds, after which the connection is closed by the If you set wireFormat.maxInactivityDuration=0 -> Inactivity monitoring is disabled when set to a value <= 0.
0 Comments
Leave a Reply. |