Some more information...
If I turn on debug logging for everything then I see the following messages
produced periodically:
2008-11-08 16:49:52,677 [nerContainer-12] DEBUG
efaultMessageListenerContainer - Consumer [ActiveMQMessageConsumer {
value=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:2:1,
started=true }] of session [PooledSession { ActiveMQSession
{id=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:2,started=true}
}] did not receive a message
2008-11-08 16:49:53,679 [nerContainer-14] DEBUG
efaultMessageListenerContainer - Consumer [ActiveMQMessageConsumer {
value=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:2:1,
started=true }] of session [PooledSession { ActiveMQSession
{id=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:2,started=true}
}] did not receive a message
2008-11-08 16:49:53,680 [nerContainer-13] DEBUG
efaultMessageListenerContainer - Consumer [ActiveMQMessageConsumer {
value=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:1:1,
started=true }] of session [PooledSession { ActiveMQSession
{id=ID:christopher-hunts-macbook-air.local-52492-1226123386415-0:0:1,started=true}
}] did not receive a message
I presume that these are heartbeat style messages.
If I then stop the external broker:
2008-11-08 16:49:54,558 [127.0.0.1:61616] DEBUG ActiveMQConnection
- Async exception with no exception listener: java.io.EOFException
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:358)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:203)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:195)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
at java.lang.Thread.run(Thread.java:613)
2008-11-08 16:49:54,562 [127.0.0.1:61616] DEBUG TcpTransport
- Stopping transport tcp://localhost/127.0.0.1:61616
...happens almost immediately.
If I then restart the broker, wait a few seconds after it is fully up, then
stop the broker again, I do not see the above stacktrace.
Any assistance is greatly appreciated as having a situation whereby my Camel
service cannot recover from an external broker not being available is a bit
of an issue for me.
Kind regards,
Christopher
--
View this message in context:
http://www.nabble.com/Camel-ActiveMQ-service-not-recovering-from-lost-broker-tp20379163s22882p20393298.html
Sent from the Camel - Users mailing list archive at Nabble.com.
