Got a Message Driven Consumer which the broker shows as connected but after a while it seems to stop accepting new messages.
Nothing amiss in the logs, the whole process just appears stalled. I have just obtained a thread dump (see https://gist.github.com/jmkgreen/8c4e399520f731c9175ee1bad969261f for this). My reading is that Camel has a single thread which is the Message Driven Consumer and that in this case it is currently blocked on a Jedis Pool? It also seems where are other ActiveMQ transports spare? We're been having issues with Jedis and connection handling - I'm wanting to narrow down what might be happening right now. Thanks, James
