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?
--
View this message in context:
http://www.nabble.com/Activemq-Consumers-Vanish-tp21062377s22882p21149645.html
Sent from the Camel - Users mailing list archive at Nabble.com.
