Issue

• Out code logic says that while calling another internal application when an exception is thrown then it stops the calling route. The shutdown strategy has been overridden with 5 sec of shutdown time.

• The scenario that was reproduced looked like the route couldn't stop completely and the message exhausted the redelivery so it went into DLQ.

• We have not configured an tranasaction route policy and the default redelivery of the exchange should be done 6 times. But before that, the message is sent to the DLQ. Do you have an example to demonstrate how TransactionErrorHandler works ?