Hello Mike,
I am indeed using 5.4.1 and I will take your advice and try to upgrade to
5.5.0.
However I think the problem may be something else. To see where exactly the
route is failing I changed my configuration a little bit:
===========================================
from("gatewayQueue:queue:OUTGOING").inOnly()
.processRef("tcpDeliverer")
.choice()
.when("someCondition").to("seda:TCP")
.otherwise().choice()
.when("anotherCondition").to("seda:HTTPDeliverer")
.when("yetAnotherCondition").to("seda:SMPP")
.otherwise();
from("seda:SMPP").inOnly().to("smpp:smppConfiguration").processRef("finalProcessorToHandleSentMessage");
from("seda:HTTPDeliverer").inOnly().processRef("processorThatSendsMessageViaHTTPPost").processRef("finalProcessorToHandleSentMessage");
from("seda:TCP").inOnly().processRef("finalProcessorToHandleSentMessage");
======================================
This time I realized that the seda:TCP consumer is hanging but the while
this happens the JMS consumer kept on flowing.
It turns out that there is some issue with the
"finalProcessorToHandleSentMessage" processor. This processor is trying to
put the message object into a cache and there seems to be some problems with
this operation.
Nevertheless I am still a little confused as to why the consumer queues stop
consuming in such a situation since in all circumstances they are inOnly.
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-queue-consumer-hangs-tp4286088p4288588.html
Sent from the Camel - Users mailing list archive at Nabble.com.
