did https://issues.apache.org/jira/browse/TOMEE-464
we can get back the old behavior using -Dtomee.webappclassloader.force-stop-phase=true wonder if it is your memory leak since in reality the scheduler threads were stopped just after the message tried on a small app and the memory seems not that bad *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* 2012/10/13 Harald Wellmann <[email protected]> > Hi Romain, > > thanks for trying to reproduce the problem! > > No, I don't do anything with Quartz config. > > The app I was using is closed source, so I can't share anything right now, > but I'll try to isolate the problem and get back. > > Best regards, > Harald > > Am 13.10.2012 17:10, schrieb Romain Manni-Bucau: > > Hi Harald, >> >> i'm not able to reproduce it. I used this ejb: >> >> @Startup >> >> @Singleton >> >> public class MyTimer { >> >> private int i = 0; >> >> >> >> @Schedule(hour = "*", minute = "*", second = "*") >> >> public void go() { >> >> System.out.println("it -> " + (i++)); >> >> } >> >> } >> >> >> i updated the class to force eclipse to reload it several times and i had >> no message of this kind. >> >> Can you share anything to let us reproduce the issue? >> >> Do you customize quartz config? >> >> >
