My last message tonight - I promise!
I have been looking into this a bit further and now understand that a
failover will connect each time. That said, a connection to a broker running
on the same machine should only take a couple of milliseconds. Indeed on my
Macbook Air here is the sequence of events:
2009-01-17 22:26:40,804 [mousIoService-6] DEBUG MinaConsumer
- Received body:
au.com.blueglue.bluegluedevices.readersocketprotocol.heartbeatnotificat...@233b8d
2009-01-17 22:26:40,804 [mousIoService-6] DEBUG DefaultTypeConverter
- Converting null -> java.lang.String with value: null
2009-01-17 22:26:40,806 [mousIoService-6] DEBUG WireFormatNegotiator
- Sending: 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]}
However on my Linux machine the above sequence takes over 100ms and goes
like this:
2009-01-17 21:56:56,572 [mousIoService-4] DEBUG MinaConsumer
- Received body:
au.com.blueglue.bluegluedevices.readersocketprotocol.heartbeatnotificat...@2728ed5f
2009-01-17 21:56:56,572 [mousIoService-4] DEBUG DefaultTypeConverter
- Converting null -> java.lang.String with value: null
2009-01-17 21:56:56,572 [mousIoService-4] DEBUG FailoverTransport
- Waking up reconnect task
2009-01-17 21:56:56,573 [mousIoService-4] DEBUG FailoverTransport
- Started.
2009-01-17 21:56:56,573 [mousIoService-4] DEBUG FailoverTransport
- Waking up reconnect task
2009-01-17 21:56:56,573 [mousIoService-4] DEBUG FailoverTransport
- Waiting for transport to reconnect.
2009-01-17 21:56:56,573 [ActiveMQ Task ] DEBUG FailoverTransport
- Attempting connect to: tcp://127.0.0.1:61616
2009-01-17 21:56:56,618 [nerContainer-62] DEBUG
efaultMessageListenerContainer - Consumer [ActiveMQMessageConsumer {
value=ID:<<some domain>-50284-1232189785356-0:0:1:1, started=true
}] of session [ActiveMQSession {id=ID:<some
domain>-50284-1232189785356-0:0:1,started=true}] did not receive a
message
2009-01-17 21:56:56,618 [nerContainer-61] DEBUG
efaultMessageListenerContainer - Consumer [ActiveMQMessageConsumer {
value=ID:<some domain>-50284-1232189785356-0:0:2:1, started=true }] of
session [ActiveMQSession {id=ID:<some
domain>-50284-1232189785356-0:0:2,started=true}] did not receive a
message
2009-01-17 21:56:56,695 [ActiveMQ Task ] DEBUG WireFormatNegotiator
- Sending: WireFormatInfo { version=3, properties={CacheSize=1024,
CacheEnabled=true, SizePrefixDisabled=false,
MaxInactivityDurationInitalDelay=10000, TcpNoDelayEnabled=true,
MaxInactivityDuration=30000, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
Why is it taking so much longer to connect to the broker on my Linux
machine? The Linux machine is much more powerful than this laptop.
Thanks for any advice.
Kind regards,
Christopher
--
View this message in context:
http://www.nabble.com/Unexpected-ActiveMQ-FailoverTransport-messages-in-my-log-tp21512906s22882p21515595.html
Sent from the Camel - Users mailing list archive at Nabble.com.
