Greetings, On Wed, Sep 25, 2013 at 12:39 PM, Romain Manni-Bucau <[email protected]> wrote: > I was not able to reproduce the "leak" on trunk but only the other issue. I > opened https://issues.apache.org/jira/browse/TOMEE-1048
Thanks for that fix, I see it has dramatically improved 1.6.0-SNAPSHOT shutdown messages about ThreadLocal resources / Threads started but not stopped. I still see a warning message when using a non-persistence @Scheduled though.. Please run 'mvn clean package tomee:run' against https://github.com/jieryn/javaee-example and then wait up to 1 minute for the timer to pop, you will see a message POP, then control-C to shut down TomEE. You should see: SEVERE: The web application [/javaee-1-SNAPSHOT] appears to have started a thread named [HSQLDB Timer @68394e81] but has failed to stop it. This is very likely to create a memory leak.
