I've seen this behaviour w/4.1, but on the consumer side. If you use failover and disable maxInactivityDuration, you disable the underlying keep alive heart beat feature, which periodically checks the connection. Therefore, if the network goes down the underlying failover transport hangs indefinitely because it never detects that the connection has been lost. So try enabling maxInactivityDuration.
Joe Mark Chaimungkalanont wrote: > > Joe, > > Thanks for the response. > > > Joe Fernandez wrote: >> >> By any chance, do you have 'maxInactivityDuration' turned off? >> > > We do indeed have set the maxInactivityDuration=0. The exact URL looks > like: > > <code> > failover:(tcp://server:54663?wireFormat.maxInactivityDuration=0)?maxReconnectAttempts=10 > </code> > > Is it the maxInactivityDuration that's causing a problem? > > Cheers, > > Mark C > > > > -- View this message in context: http://www.nabble.com/Sending-message-hangs-when-negotiating-wire-format-tp19717526p19734684.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
