I have resolved the issue.. It is an issue with quartz component. Quartz was
being shutdown but the webapp didn't wait for quartz to finish before it
shutdown so Tomcat decided that it had left threads running and complained.
So, i override the shutdown method in quartzcomponent as follows and it
worked for me..
@Override
public void shutdown() throws SchedulerException, InterruptedException {
Scheduler scheduler = super.getScheduler();
if (scheduler != null) {
scheduler.shutdown(true);
Thread.sleep(1000);
scheduler = null;
}
}
Note the boolean argument to shutdown is the vital part. If you remove that
true to call the no-arg version or set it to false, your webapp won't wait
for quartz to shudown before it shuts down.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5770634.html
Sent from the Camel - Users mailing list archive at Nabble.com.
