Hi, I would like to understand more how Camel handles messages during shutdown.
In my app. I have just single route which is connected to IBM Websphere and processes given queue. One thing we did not fully understand is what is actually happening when consuming the queue in TRANSACTED mode and while shutdown signal is sent. It seems like during the shutdown period (waiting for inflight messages to complete) some new messages are rejected and picked up again and rejected - however the rejection increases JMSXDeliveryCount header so messages are forwarded to BACKOUT queue despite there is nothing wrong with them. I would expect that once shutdown is signaled all idle threads are immediately stopped so no new work can be accepted (to be then rejected) and only busy threads are allowed to complete their inflight message within the timeout (300 sec.). Can someone explain if above may be happening and if so advise some way how to address it? The goal is to not increase delivery counts because of shutdown - we want to reject/rollback message only in case there is a problem (exception thrown during route flow). Thanks a lot P. -- View this message in context: http://camel.465427.n5.nabble.com/Message-rejection-during-graceful-shutdown-tp5753530.html Sent from the Camel - Users mailing list archive at Nabble.com.
