;
}
}
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
akram.s...@gmail.com
À: users@camel.apache.org
Envoyé: Mercredi 12 Août 2015 23:11:41
Objet: Re: Camel quartz memory leak
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
I am using camel 2.15.1. Stopping the route using JMX, againg restarting it
using JMX. Also the same getting same error if I restart entire camel
context.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5768275.html
Sent from the Camel
if I restart entire camel
context.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5768275.html
Sent from the Camel - Users mailing list archive at Nabble.com.
org.apache.catalina.loader.WebappClassLoaderBase
clearReferencesThreads
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter
Method)
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
Jun 10, 2015 10:01:03 AM org.apache.catalina.loader.WebappClassLoaderBase
clearReferencesThreads
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063.html
Sent
