you mean with persistence the timer is here when you restart right? *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/5 tschuler <[email protected]> > Hi Romain! > > I have to correct me: > The calendar timer is removed after successful firing only if no quartz > persistence is configured. > It still happens if quartz calendar triggers are stored in a database. > > Best regards, > Thomas > > ----- > > Hi Romain! > > As I can see you fixed both issues - am I right? > Using the TomEE 1.6.0 snapshot from today: > - the interval timer starts firing as expected > - the calendar timer is removed after successful firing > > Best regards, > Thomas > > Von: Romain Manni-Bucau [via OpenEJB] [mailto: > [email protected]] > Gesendet: Freitag, 2. August 2013 16:38 > An: Thomas Schuler > Betreff: Re: Fired calendar trigger still available > > 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 <[hidden > email]</user/SendEmail.jtp?type=node&node=4664498&i=0>> > > > 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. > > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://openejb.979440.n4.nabble.com/Fired-calendar-trigger-still-available-tp4664493p4664498.html > To unsubscribe from Fired calendar trigger still available, click here< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4664493&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjQ0OTN8LTE4NTIyNTQ0OTI= > >. > NAML< > http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Fired-calendar-trigger-still-available-tp4664493p4664520.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
