-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
Documentation (Ref Guide, User Guide, etc.)
-
-
-
-
-
-
+
-
The customer is having a cluster with two nodes in a domain setup. They have auto timer like below in @Singleton, @Startup EJBs:
@Singleton @Startup public class xxx { @Schedule(second= "*/30", minute = "*", hour = "*", dayOfWeek = "*", month = "*", year = "*", persistent = true) public void schedule() { ... }
In some cases (race condition?) the timer is created twice in the database, see attached files.
Is this a known issue?
- causes
-
JBEAP-23510 [GSS](7.4.z) NPE when EJB Database Timer Persistence adjustCreateAutoTimerStatement is called
- Closed
- incorporates
-
WFLY-15569 Database persistent auto timer are created twice
- Closed
- is related to
-
JBEAP-23007 (7.4.z) WFLY-15583 - Adjust sql statements during initialization of DatabaseTimerPersistence
- Closed
-
JBEAP-23008 (7.4.z) WFLY-15335 - Simplify the processing of ejb timer timeout method params
- Closed
-
JBEAP-23009 (7.4.z) WFLY-15499 - Honor sybase as database value, and remove the unused field databaseDialects in DatabaseTimerPersistence class
- Closed