Romain Manni-Bucau wrote > 2016-11-14 11:01 GMT+01:00 jessepeng <
> jan_pien@ > > > > Which reloading mode? JMX/plain tomcat or eclipse? It's only happening in eclipse reloading mode. Using the normal tomcat manager, it works fine. I do have a couple of warnings regarding failed stopping of started threads, though (although it seems to be a different issue): WARNUNG - The web application [poweb-web] appears to have started a thread named [ForkJoinPool.commonPool-work er-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.ForkJoinPool.awaitWork(ForkJoinPool.java:1824) java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1693) java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) WARNUNG - The web application [poweb-web] appears to have started a thread named [ForkJoinPool.commonPool-work er-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.ForkJoinPool.awaitWork(ForkJoinPool.java:1824) java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1693) java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) WARNUNG - The web application [poweb-web] appears to have started a thread named [ForkJoinPool.commonPool-work er-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: sun.misc.Unsafe.park(Native Method) java.util.concurrent.ForkJoinPool.awaitWork(ForkJoinPool.java:1824) java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1693) java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/IllegalAccess-exception-when-reloading-TomEE-7-0-1-using-Apache-Camel-2-18-0-tp4680514p4680527.html Sent from the TomEE Users mailing list archive at Nabble.com.
