Hi, about 2 it can be a "no luck" case, i commited a test case on this case and updated a bit the logic, if you can test on next trunk it would be great.
*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/8/2 tschuler <[email protected]> > Hi! > > We are doing some tests on TomEE 1.6.0 snapshot. > > We use a scheduled bean that gets fired by a calendar timer > (timerService.createCalendarTimer()). > After ejbTimeout happens, the according timer is still available > (timerService.getTimers()). > This is the case only if quartz persistence is activated. Might this be a > potential memory leak? > > Another observation we made for interval timer > (timerService.createIntervalTimer): > It often gets fired immediately after creation. It seems that the > initialDuration (or the first expiration date) is ignored. Once the > immedialely firing happens, it happens for all interval timer created > afterwards too. > Quartz persistence may be activated or not - it does not make a difference. > > Best regards, > Thomas > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fired-calendar-trigger-still-available-tp4664493.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
