You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Rural Hunter <ru...@gmail.com> on 2014/01/29 08:35:45 UTC
Camel 2.12.2 crashes on activemq restart
Hi,
My route is quite simple:
from(REQUEST_QUEUE).process(processor1).process(processor2).process(processor3).to(COMPLETE_QUEUE)
REQUEST_QUEUE and COMPLETE_QUEUE are both activemq queues. It runs fine
normaly. But when I restart activmq, I found my Camel application just
exited with this log:
2014-01-29 15:23:02 WARN Camel (camel-1) thread #0 -
JmsConsumer[queue.request]
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer -
Setup of JMS message listener invoker failed for destination
'queue.request' - trying to recover. Cause: java.io.EOFException
2014-01-29 15:23:02 WARN Camel (camel-1) thread #2 -
JmsConsumer[queue.complete]
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer -
Setup of JMS message listener invoker failed for destination
'queue.complete' - trying to recover. Cause: java.io.EOFException
2014-01-29 15:23:02 ERROR Camel (camel-1) thread #2 -
JmsConsumer[queue.complete]
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer -
Could not refresh JMS Connection for destination 'queue.complete' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection
refused.
2014-01-29 15:23:02 ERROR Camel (camel-1) thread #0 -
JmsConsumer[queue.request]
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer -
Could not refresh JMS Connection for destination 'queue.request' -
retrying in 5000 ms. Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection
refused.
I tried to use failover broker url(failover:tcp://localhost:61616) but
same thing happened. I also tried to use jms component instead of
activemq component but still got the same result.
Re: Camel 2.12.2 crashes on activemq restart
Posted by Rural Hunter <ru...@gmail.com>.
Anyone?
Re: Camel 2.12.2 crashes on activemq restart
Posted by Rural Hunter <ru...@gmail.com>.
No, as I said, camel crashed with that error. I had to restart camel.
于 2014/1/29 16:00, Willem Jiang 写道:
> This warning messages are expected.
> Does the camel route work again when the ActiveMQ server
> is back online ?
>
> --
>
Re: Camel 2.12.2 crashes on activemq restart
Posted by Willem Jiang <wi...@gmail.com>.
This warning messages are expected.
Does the camel route work again when the ActiveMQ server
is back online ?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On January 29, 2014 at 3:36:27 PM, Rural Hunter (ruralhunter@gmail.com) wrote:
>
> Hi,
>
> My route is quite simple:
> from(REQUEST_QUEUE).process(processor1).process(processor2).process(processor3).to(COMPLETE_QUEUE)
> REQUEST_QUEUE and COMPLETE_QUEUE are both activemq queues.
> It runs fine
> normaly. But when I restart activmq, I found my Camel application
> just
> exited with this log:
>
> 2014-01-29 15:23:02 WARN Camel (camel-1) thread #0 -
> JmsConsumer[queue.request]
> org.apache.camel.component.jms.DefaultJmsMessageListenerContainer
> -
> Setup of JMS message listener invoker failed for destination
> 'queue.request' - trying to recover. Cause: java.io.EOFException
> 2014-01-29 15:23:02 WARN Camel (camel-1) thread #2 -
> JmsConsumer[queue.complete]
> org.apache.camel.component.jms.DefaultJmsMessageListenerContainer
> -
> Setup of JMS message listener invoker failed for destination
> 'queue.complete' - trying to recover. Cause: java.io.EOFException
> 2014-01-29 15:23:02 ERROR Camel (camel-1) thread #2 -
> JmsConsumer[queue.complete]
> org.apache.camel.component.jms.DefaultJmsMessageListenerContainer
> -
> Could not refresh JMS Connection for destination 'queue.complete'
> -
> retrying in 5000 ms. Cause: Could not connect to broker URL:
> tcp://localhost:61616. Reason: java.net.ConnectException:
> Connection
> refused.
> 2014-01-29 15:23:02 ERROR Camel (camel-1) thread #0 -
> JmsConsumer[queue.request]
> org.apache.camel.component.jms.DefaultJmsMessageListenerContainer
> -
> Could not refresh JMS Connection for destination 'queue.request'
> -
> retrying in 5000 ms. Cause: Could not connect to broker URL:
> tcp://localhost:61616. Reason: java.net.ConnectException:
> Connection
> refused.
>
> I tried to use failover broker url(failover:tcp://localhost:61616)
> but
> same thing happened. I also tried to use jms component instead
> of
> activemq component but still got the same result.
>
Re: Camel 2.12.2 crashes on activemq restart
Posted by Rural Hunter <ru...@gmail.com>.
Of coz I can. The error occurred during activemq restarting and then
camel crashed. After activemq is restarted, I had to restart my camel
application since it crashed during the activemq restarting.
于 2014/1/29 15:57, Charles Moulliard 写道:
> The problem is not related to Camel. Can you make a JMS test to verify that
> you can connect to your ActiveMQ broker or using ant (
> http://activemq.apache.org/examples.html). This is why you get this error
> messages from Camel/spring : Cause: Could not connect to broker URL:
> tcp://localhost:61616. Reason: java.net.ConnectException: Connection
> refused.
>
>
>
Re: Camel 2.12.2 crashes on activemq restart
Posted by Charles Moulliard <ch...@gmail.com>.
The problem is not related to Camel. Can you make a JMS test to verify that
you can connect to your ActiveMQ broker or using ant (
http://activemq.apache.org/examples.html). This is why you get this error
messages from Camel/spring : Cause: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection
refused.
On Wed, Jan 29, 2014 at 8:35 AM, Rural Hunter <ru...@gmail.com> wrote:
> Hi,
>
> My route is quite simple:
> from(REQUEST_QUEUE).process(processor1).process(processor2).process(
> processor3).to(COMPLETE_QUEUE)
> REQUEST_QUEUE and COMPLETE_QUEUE are both activemq queues. It runs fine
> normaly. But when I restart activmq, I found my Camel application just
> exited with this log:
>
> 2014-01-29 15:23:02 WARN Camel (camel-1) thread #0 -
> JmsConsumer[queue.request] org.apache.camel.component.jms.
> DefaultJmsMessageListenerContainer - Setup of JMS message listener
> invoker failed for destination 'queue.request' - trying to recover. Cause:
> java.io.EOFException
> 2014-01-29 15:23:02 WARN Camel (camel-1) thread #2 -
> JmsConsumer[queue.complete] org.apache.camel.component.jms.
> DefaultJmsMessageListenerContainer - Setup of JMS message listener
> invoker failed for destination 'queue.complete' - trying to recover. Cause:
> java.io.EOFException
> 2014-01-29 15:23:02 ERROR Camel (camel-1) thread #2 -
> JmsConsumer[queue.complete] org.apache.camel.component.jms.
> DefaultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'queue.complete' - retrying in 5000 ms. Cause: Could not
> connect to broker URL: tcp://localhost:61616. Reason:
> java.net.ConnectException: Connection refused.
> 2014-01-29 15:23:02 ERROR Camel (camel-1) thread #0 -
> JmsConsumer[queue.request] org.apache.camel.component.jms.
> DefaultJmsMessageListenerContainer - Could not refresh JMS Connection for
> destination 'queue.request' - retrying in 5000 ms. Cause: Could not connect
> to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException:
> Connection refused.
>
> I tried to use failover broker url(failover:tcp://localhost:61616) but
> same thing happened. I also tried to use jms component instead of activemq
> component but still got the same result.
>
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io