I have failover in my app. But some times it stops.
I use activeMQ version 5.1, boker url is
failover://(ssl://<ip>?wireFormat.maxInactivityDuration=-1)?maxReconnectDelay=2000,
transportListener on ActiveMQConnectionFactory and timer task that restarts
listener every 15 mins. And I have in log that FailoverTransport stopped:
<Message>10:16:33:987|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:130|Call start() for
connection for jmsListener_m finished</Message>
<Message>10:16:33:987|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:131|Start create session
from connection_jms</Message>
<Message>10:16:33:987|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:133|Stop create session
from connection_jms</Message>
<Message>10:16:33:987|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:135|Start jms listener
(jmsListener_m) for queue "queue1"</Message>
<Message>10:16:34:049|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:137|Call start() for
jmsListener_m finished</Message>
<Message>10:16:34:049|INFO
|timerFactory|cl.JMSListenersManager:initAndStart:165|Set clientId
"-f210da7:11ef481504e:-7ffd" for connection</Message>
<Message>10:30:11:539|DEBUG|http-8081-Processor25|org.apache.activemq.transport.failover.FailoverTransport:reconnect:531|Waking
up reconnect task</Message>
<Message>10:30:11:539|DEBUG|http-8081-Processor25|org.apache.activemq.transport.failover.FailoverTransport:start:228|Started.</Message>
<Message>10:30:11:539|DEBUG|http-8081-Processor25|org.apache.activemq.transport.failover.FailoverTransport:reconnect:531|Waking
up reconnect task</Message>
<Message>10:30:11:539|DEBUG|ActiveMQ
Task|org.apache.activemq.transport.failover.FailoverTransport:doReconnect:671|Attempting
connect to: ssl://<ip>?wireFormat.maxInactivityDuration=-1</Message>
<Message>10:30:11:617|DEBUG|ActiveMQ
Task|org.apache.activemq.transport.WireFormatNegotiator:start:77|Sending:
WireFormatInfo { version=3, properties={TightEncodingEnabled=true,
CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false,
StackTraceEnabled=true, MaxInactivityDurationInitalDelay=10000,
MaxInactivityDuration=-1, CacheEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}</Message>
<Message>10:30:17:320|DEBUG|ActiveMQ Transport:
ssl:///<ip>|org.apache.activemq.transport.WireFormatNegotiator:onCommand:108|Received
WireFormat: WireFormatInfo { version=3,
properties={TightEncodingEnabled=true, CacheSize=1024,
TcpNoDelayEnabled=true, SizePrefixDisabled=false, StackTraceEnabled=true,
MaxInactivityDurationInitalDelay=10000, MaxInactivityDuration=30000,
CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}</Message>
<Message>10:30:17:320|DEBUG|ActiveMQ Transport:
ssl:///<ip>|org.apache.activemq.transport.WireFormatNegotiator:onCommand:115|ssl://<ip>
before negotiation: OpenWireFormat{version=3, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false,
sizePrefixDisabled=false}</Message>
<Message>10:30:17:320|DEBUG|ActiveMQ Transport:
ssl:///<ip>|org.apache.activemq.transport.WireFormatNegotiator:onCommand:130|ssl://<ip>
after negotiation: OpenWireFormat{version=3, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true,
sizePrefixDisabled=false}</Message>
<Message>10:30:17:320|DEBUG|ActiveMQ
Task|org.apache.activemq.transport.failover.FailoverTransport:doReconnect:680|Connection
established</Message>
<Message>10:30:17:320|INFO |ActiveMQ
Task|org.apache.activemq.transport.failover.FailoverTransport:doReconnect:691|Successfully
connected to ssl://<ip>?wireFormat.maxInactivityDuration=-1</Message>
<Message>10:30:23:836|DEBUG|http-8081-Processor25|org.apache.activemq.transport.failover.FailoverTransport:stop:246|Stopped.</Message>
<Message>10:30:23:836|DEBUG|http-8081-Processor25|org.apache.activemq.transport.tcp.TcpTransport:doStop:437|Stopping
transport ssl://<ip></Message>
Why does failover stop? Why don't I have invocation in transportInterupted()
method of transport listener?
--
View this message in context:
http://www.nabble.com/FailoverTransport-stops-unexpectedly-and-message-listener-doesn%27t-receive-messages-tp21579536p21579536.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
