Client problem recovering from a restart of a broker

[amiko <ro...@hotmail.com>]

Hi

We're using activemq 5.1.0, the client connects to the broker using
failover:
new ActiveMQConnectionFactory( "failover:" + brokerUri );

The problem is that after the brokers restart there seems to be a problem
with the reconnect of the client (Received unexpected response for command
id ...)


2008-12-08 18:04:25,201 DEBUG
org.apache.activemq.transport.failover.FailoverTransport [ActiveMQ Task]-
Attempting connect to: tcp://ildev3:61616
2008-12-08 18:04:25,202 DEBUG
org.apache.activemq.transport.WireFormatNegotiator [ActiveMQ Task]- Sending:
WireFormatInfo { version=3, properties={CacheSize=
1024, CacheEnabled=true, SizePrefixDisabled=false,
MaxInactivityDurationInitalDelay=10000, TcpNoDelayEnabled=true,
MaxInactivityDuration=30000, TightEncoding
Enabled=true, StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2008-12-08 18:04:25,205 DEBUG
org.apache.activemq.transport.WireFormatNegotiator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- Received WireFormat:
WireFormatInfo { version=3, properties={CacheSize=1024, CacheEnabled=true,
SizePrefixDisabled=false, MaxInactivityDurationInitalDelay=10000,
TcpNoDelayEnable
d=true, MaxInactivityDuration=0, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
2008-12-08 18:04:25,205 DEBUG
org.apache.activemq.transport.WireFormatNegotiator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- tcp://ildev3/172.16.0
.107:61616 before negotiation: OpenWireFormat{version=3, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}
2008-12-08 18:04:25,205 DEBUG
org.apache.activemq.transport.WireFormatNegotiator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- tcp://ildev3/172.16.0
.107:61616 after negotiation: OpenWireFormat{version=3, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true, sizePrefixDisabled=false}
2008-12-08 18:04:25,206 DEBUG
org.apache.activemq.transport.failover.FailoverTransport [ActiveMQ Task]-
Connection established
2008-12-08 18:04:25,206 INFO 
org.apache.activemq.transport.failover.FailoverTransport [ActiveMQ Task]-
Successfully reconnected to tcp://ildev3:61616
2008-12-08 18:04:25,217 DEBUG
org.apache.activemq.transport.ResponseCorrelator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- Received unexpected res
ponse: {Response {commandId = 0, responseRequired = false, correlationId =
1}}for command id: 1
2008-12-08 18:04:25,222 DEBUG
org.apache.activemq.transport.ResponseCorrelator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- Received unexpected res
ponse: {Response {commandId = 0, responseRequired = false, correlationId =
4}}for command id: 4
2008-12-08 18:04:25,227 DEBUG
org.apache.activemq.transport.ResponseCorrelator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- Received unexpected res
ponse: {Response {commandId = 0, responseRequired = false, correlationId =
5}}for command id: 5
2008-12-08 18:04:25,244 DEBUG
org.apache.activemq.transport.ResponseCorrelator [ActiveMQ Transport:
tcp://ildev3/172.16.0.107:61616]- Received unexpected res
ponse: {Response {commandId = 0, responseRequired = false, correlationId =
2}}for command id: 2
2

Thank you for your help
Ami
-- 
View this message in context: http://www.nabble.com/Client-problem-recovering-from-a-restart-of-a-broker-tp20909869p20909869.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.