As documented in the SEDA endpoint, the solution was to reduce pollTimeout
from 1 second down to a small number, but this results in more CPU being
consumed while the system is in the idle state waiting for work.  I may need
to play with the DefaultShutdownStrategy to possibly do an interrupt
first...



--
View this message in context: 
http://camel.465427.n5.nabble.com/CamelContext-shutdown-takes-a-long-time-almost-a-second-per-route-tp5766595p5766597.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to