The code that pointed out is in java.io.PipedInputStream.read(). I believe Camel's thread management is triggering an infinite loop in it, although I am not certain.
Is there a graceful way to have a Camel polling route completely reset itself periodically? Or is bouncing the container a better option? Thanks, -neil -- View this message in context: http://camel.465427.n5.nabble.com/Camel-s-use-of-jsch-java-io-tp5740623p5740700.html Sent from the Camel - Users mailing list archive at Nabble.com.
