Description
See
https://issues.apache.org/jira/browse/AMQ-5310
When shutting down a Camel app etc that connects to a AMQ broker either embedded or remotely, then during that shutdown phase, the message listener container may try to accept new messages, as it has not yet been shutdown, but Camel is being stopped. And during that work the connection to the broker may not be valid and a failover is being done by spring jms. And if that work fails such as thrown some non JMSException then we can get stuck.
To help this we can stop listening quicker in camel-jms, by detecting that we are stopping CamelContext and not allow running. This can be done as the acceptMessagesWhileStopping is default false also.