Hi If you close the cache with the app this shouldnt occur (disk and auxilary caches case). If yes that's a jcs issue. I'll try to check how are managed started thread tonight.
Side note (surely obvious but writing it down): RemoteServer is not designed to be embed in tomee but to run in its own jvm. Le 1 juin 2014 00:03, "hwaastad" <[email protected]> a écrit : > OK, > got it working. > > My last and *absolutely final question* is regarding stopping tomee when > using disk and tcp lateral. > > (If this still is a JCS issue so just ignore this.) > > br hw > > > > SEVERE - The web application [] appears to have started a thread named > [JCS-Scheduler-Thread-25] but has failed to stop it. This is very likely to > create a memory leak. > SEVERE - The web application [] appears to have started a thread named > [JCS-Scheduler-Thread-26] but has failed to stop it. This is very likely to > create a memory leak. > SEVERE - The web application [] appears to have started a thread named > [Thread-27] but has failed to stop it. This is very likely to create a > memory leak. > SEVERE - The web application [] appears to have started a thread named > [Thread-28] but has failed to stop it. This is very likely to create a > memory leak. > SEVERE - The web application [] appears to have started a thread named > [JCS-Scheduler-Thread-29] but has failed to stop it. This is very likely to > create a memory leak. > SEVERE - The web application [] appears to have started a thread named > [JCS-Scheduler-Thread-30] but has failed to stop it. This is very likely to > create a memory leak. > SEVERE - The web application [] appears to have started a thread named > [JCS-UDPDiscoveryReceiver-Thread-31] but has failed to stop it. This is > very > likely to create a memory leak. > SEVERE - The web application [] appears to have started a thread named > [JCS-UDPDiscoveryReceiver-Thread-32] but has failed to stop it. This is > very > likely to create a memory leak. > INFO - Stopping ProtocolHandler ["http-bio-8080"] > INFO - Stopping ProtocolHandler ["ajp-bio-8009"] > INFO - Stopping server services > INFO - Undeploying app: openejb > INFO - Destroying ProtocolHandler ["http-bio-8080"] > INFO - Destroying ProtocolHandler ["ajp-bio-8009"] > Exception in thread "Thread-24" java.lang.NoClassDefFoundError: > org/apache/commons/jcs/auxiliary/disk/AbstractDiskCache$1 > at > > org.apache.commons.jcs.auxiliary.disk.AbstractDiskCache.dispose(AbstractDiskCache.java:456) > at > > org.apache.commons.jcs.engine.control.CompositeCache.dispose(CompositeCache.java:1359) > at > > org.apache.commons.jcs.engine.control.CompositeCacheManager.freeCache(CompositeCacheManager.java:637) > at > > org.apache.commons.jcs.engine.control.CompositeCacheManager.freeCache(CompositeCacheManager.java:624) > at > > org.apache.commons.jcs.engine.control.CompositeCacheManager.shutDown(CompositeCacheManager.java:686) > at > > org.apache.commons.jcs.engine.control.CompositeCacheManager$ShutdownHook.run(CompositeCacheManager.java:974) > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.jcs.auxiliary.disk.AbstractDiskCache$1 > at > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720) > at > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571) > at > > org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:120) > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/jcs-jcache-and-tomee-tp4669737p4669778.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
