You read my mind :-)
from("jetty:http://localhost:8085/incoming?sessionSupport=true";).routeId("Jetty
Endpoint to ActiveMQ")
.setExchangePattern(ExchangePattern.InOut)
.to("activemq:incoming?replyTo=outgoing&replyToType=Exclusive");
I have not been able to reproduce the full "stop the world" exception yet.
But the message below did come up and I was able to continue testing through
it. My concern with using Exclusive queues is that I lose full
clusterability (I kind of need it).
Exception that does not stop JMS processing
2013-01-11 11:37:10,903 [ger[outgoing]-1] WARN
tQueueMessageListenerContainer - Setup of JMS message listener invoker
failed for destination 'outgoing' - trying to recover. Cause: The Consumer
is closed
2013-01-11 11:37:10,908 [sumer[incoming]] WARN
ultJmsMessageListenerContainer - Setup of JMS message listener invoker
failed for destination 'incoming' - trying to recover. Cause: The Consumer
is closed
2013-01-11 11:37:10,921 [sumer[incoming]] INFO
ultJmsMessageListenerContainer - Successfully refreshed JMS Connection
2013-01-11 11:37:10,922 [ger[outgoing]-1] INFO
tQueueMessageListenerContainer - Successfully refreshed JMS Connection
--
View this message in context:
http://camel.465427.n5.nabble.com/Jetty-to-ActiveMQ-Failure-tp5725323p5725410.html
Sent from the Camel - Users mailing list archive at Nabble.com.
