I have an ActiveMQ 4.1.1 broker and client. Sometimes a client hangs in the
middle of the wireformat negotiation, and does not recognize that it is
stuck. This does not happen all the time, but once we did have about 10% of
800 clients freeze overnight. Client logs:
2007-12-13 01:08:16,917 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - Thread-3 -
Waking up reconnect task
2007-12-13 01:08:16,965 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - ActiveMQ Task -
Attempting connect to:
tcp://**.*.*.*:**?wireFormat.maxInactivityDuration=600000&soTimeout=10000
2007-12-13 01:08:17,232 DEBUG
[org.apache.activemq.transport.WireFormatNegotiator] - ActiveMQ Task -
Sending: WireFormatInfo { version=2, properties={CacheSize=1024,
CacheEnabled=true, SizePrefixDi sabled=false, TcpNoDelayEnabled=true,
MaxInactivityDuration=600000, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2007-12-13 01:08:17,236 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - ActiveMQ Task -
Connection established
2007-12-13 01:08:17,237 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - Thread-3 -
Started.
2007-12-13 01:08:17,240 INFO
[com.highergear.lead.jms.JMSFactoryConnectionUtil] - Thread-3 - Created
Connection
... That's all it says for hours.
Upon restarting both broker and client:
2007-12-13 08:46:40,633 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - Thread-3 -
Waking up reconnect task
2007-12-13 08:46:40,680 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - ActiveMQ Task -
Attempting connect to:
tcp://**.*.*.*:**?wireFormat.maxInactivityDuration=600000&soTimeout=10000
2007-12-13 08:46:40,955 DEBUG
[org.apache.activemq.transport.WireFormatNegotiator] - ActiveMQ Task -
Sending: WireFormatInfo { version=2, properties={CacheSize=1024,
CacheEnabled=true, SizePrefixDi sabled=false, TcpNoDelayEnabled=true,
MaxInactivityDuration=600000, TightEncodingEnabled=true,
StackTraceEnabled=true}}, magic=[A,c,t,i,v,e,M,Q]}
2007-12-13 08:46:40,959 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - ActiveMQ Task -
Connection established
2007-12-13 08:46:40,961 DEBUG
[org.apache.activemq.transport.failover.FailoverTransport] - Thread-3 -
Started.
2007-12-13 08:46:40,963 INFO
[com.highergear.lead.jms.JMSFactoryConnectionUtil] - Thread-3 - Created
Connection
2007-12-13 08:46:40,999 DEBUG
[org.apache.activemq.transport.WireFormatNegotiator] - ActiveMQ Transport:
tcp:///**.*.*.*:** - Received WireFormat: WireFormatInfo { version=2,
properties={Cache Size=1024, CacheEnabled=true, SizePrefixDisabled=false,
TcpNoDelayEnabled=false, MaxInactivityDuration=600000,
TightEncodingEnabled=false, StackTraceEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
2007-12-13 08:46:41,001 DEBUG
[org.apache.activemq.transport.WireFormatNegotiator] - ActiveMQ Transport:
tcp:///**.*.*.*:** - tcp:///**.*.*.*:** before negotiation:
OpenWireFormat{version =2, cacheEnabled=false, stackTraceEnabled=false,
tightEncodingEnabled=false, sizePrefixDisabled=false}
2007-12-13 08:46:41,001 DEBUG
[org.apache.activemq.transport.WireFormatNegotiator] - ActiveMQ Transport:
tcp:///**.*.*.*:** - tcp:///**.*.*.*:** after negotiation:
OpenWireFormat{version= 2, cacheEnabled=true, stackTraceEnabled=true,
tightEncodingEnabled=false, sizePrefixDisabled=false}
2007-12-13 08:46:41,158 INFO
[com.highergear.lead.jms.JMSFactoryConnectionUtil] - Thread-3 - Started
Connection
The WireFormatNegotiation is not completing and no timeout occurs that
allows the client to recognize the connection is bad.
Any and all suggestions would be appreciated.
--
View this message in context:
http://www.nabble.com/WireFormat-Negotiation-Hangs-in-4.1.1-tp14457282s2354p14457282.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
