Since the JMS consumer is based on the Spring jms MessageListenerContainer, I don't think camel will disconnect the consumer itself. Maybe the ActiveMQ will close it with a connection timeout exception.
Willem bwtaylor wrote: > We have a theory that work done within our Camel route may be experiencing a > database locking issue. We haven't confirmed this yet, but it begs the > question... What would ActiveMQ and/or Camel do with a camel processor that > effectively hangs waiting (forever) for a deadlock to resolve. Is there > anything in ActiveMQ or Camel that would disconnect such a consumer?
