tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars-Fredrik Smedberg <itsme...@gmail.com>
Subject Question regarding EJB Timers
Date Thu, 06 Nov 2014 13:22:20 GMT
Hi

I've been looking for some details on EJB Timers and retries... maybe
someone can help me out on the below?


- WebSphere has default an unlimited number of retries with a 300 sec (5
min) interval.
- Assume we have a timer that triggers every half hour and that it at some
point fails (lets assume 1 clock for the example below)
- Only thing I can find the EJB JSR318 EJB 3.1 is:

  - "If the container-managed transaction is rolled back, the container
retries the timeout." and
  - "The container must retry the timeout after the transaction rollback."
and
  - "If the transaction fails or is rolled back, the container must retry
the timeout at least once."

Questions

- Are all details around retries implementation specific? How does OpenEJB
handle it?
- Assume that the timer tasks all fail before say 1:30, will I then see the
following scenario??

  - 1:00 - Timer due to @Schedule expression => Fails
  - 1:05 -> 1:25 (every 5 minutes) - Timer due to retry => Fails
  - 1:30 - Timer due to @Schedule expression => Succeed
  - 2:00 - Timer due to @Schedule expression => Succeed
  - ... and so on...

- Or might the Timer trigger twice (or twice within a short timeinterval
around) 2:00 ?
- Will the retry of the Timer stop as soon as the Timer not fails
regardless of wether it was triggered as a result of a retry or a normal
@Scheduler?



-- 
Med vänlig hälsning / Best regards

Lars-Fredrik Smedberg

STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
address(es) and may contain confidential or privileged information. If
you are not the intended recipient, please notify Lars-Fredrik Smedberg
immediately at itsmeden@gmail.com, and destroy all copies of this
message and any attachments.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message