Hi! It seems that it happens with the manager also. I've just seen this in my logs:
25-Sep-2013 14:42:30.137 SEVERE [localhost-startStop-3] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/manager] appears to have started a thread named [StatelessPool.worker.1] but has failed to stop it. This is very likely to create a memory leak. 25-Sep-2013 14:42:30.138 SEVERE [localhost-startStop-3] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/manager] appears to have started a thread named [StatelessPool.worker.2] but has failed to stop it. This is very likely to create a memory leak. 25-Sep-2013 14:42:30.138 SEVERE [localhost-startStop-3] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/manager] appears to have started a thread named [StatelessPool.worker.3] but has failed to stop it. This is very likely to create a memory leak. 25-Sep-2013 14:42:30.138 SEVERE [localhost-startStop-3] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/manager] appears to have started a thread named [StatelessPool.worker.4] but has failed to stop it. This is very likely to create a memory leak. 25-Sep-2013 14:42:30.138 SEVERE [localhost-startStop-3] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/manager] appears to have started a thread named [StatelessPool.worker.5] but has failed to stop it. This is very likely to create a memory leak. This should be enough for testing. Otherwise I'll try to make a demo project, but maybe it's not necessary. ________________________________ From: Romain Manni-Bucau [via OpenEJB] <[email protected]> To: zmirc <[email protected]> Sent: Wednesday, September 25, 2013 10:46 AM Subject: Re: Memory leak by openejb.pool.scheduler Hi can you push us a sample reproducing it please? *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/25 zmirc <[hidden email]> > Hi! > > No, I didn't configure anything. Just using @Schedule on @Singleton. > > > PS, you couldn't see my edit because Nabble doesn't send it over e-mail: > "The problem is that I can't stop the server in production (on linux) > because of that. It just doesn't stop most of the time, especially after I > redeploy the app once." > > > > ________________________________ > From: Romain Manni-Bucau [via OpenEJB] < > [hidden email]> > To: zmirc <[hidden email]> > Sent: Wednesday, September 25, 2013 6:43 AM > Subject: Re: Memory leak by openejb.pool.scheduler > > > > Hi > > Do you configure quartz? > Le 25 sept. 2013 00:17, "zmirc" <[hidden email]> a écrit : > > > > Hi! > > Using Tomee 1.6.0 2013.09.20, I get this when I try to stop Tomee, which > > has > > a ROOT application that uses EJB @Schedule: > > > > 25-Sep-2013 00:06:09.745 WARNING [localhost-startStop-2] > > org.apache.openejb.assembler.classic.Assembler.destroyApplication > > Application id 'ROOT' not found in: [openejb] > > 25-Sep-2013 00:06:09.748 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.37] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.748 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.38] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.748 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.39] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.748 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.40] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.749 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.41] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.749 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.42] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.749 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.43] but has failed to stop it. This is > > very likely to create a memory leak. > > 25-Sep-2013 00:06:09.749 SEVERE [localhost-startStop-2] > > org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The > web > > application [] appears to have started a thread named > > [org.apache.openejb.pool.scheduler.44] but has failed to stop it. This is > > very likely to create a memory leak. > > > > This don't happen with 1.5.2 nor with previous versions of 1.6.0 (some > from > > August - I don't remember which versions) > > > > > > > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > > > > ________________________________ > > If you reply to this email, your message will be added to the discussion > below: > http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665267.html > To unsubscribe from Memory leak by openejb.pool.scheduler, click here. > NAML > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665272.html > Sent from the OpenEJB User mailing list archive at Nabble.com. > ________________________________ If you reply to this email, your message will be added to the discussion below:http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665276.html To unsubscribe from Memory leak by openejb.pool.scheduler, click here. NAML -- View this message in context: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4665263p4665286.html Sent from the OpenEJB User mailing list archive at Nabble.com.
