-
Bug
-
Resolution: Done
-
Blocker
-
7.0.0.GA, 7.0.1.GA, 7.0.2.GA, 7.0.3.GA
-
Compatibility/Configuration, User Experience
-
-
-
-
-
-
Medium
-
Workaround Exists
-
-
If the transaction isolation level is set to SERIALIZABLE if one node aquires the row lock via the
UPDATE JBOSS_EJB_TIMER..
the other nodes throw an
ORA-08177: can't serialize access for this transaction
exception.
The timer thats row threw the exception never runs any more, not even in case the other nodes were shut down.
The serialization exception is also thrown upon server/application startup sometimes.
- clones
-
WFLY-6412 Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g
- Closed
- is cloned by
-
WFLY-9239 [GSS](7.1.0) Timer fails if transaction isolation set to SERIALIZABLE
- Closed
-
JBEAP-8715 [GSS](7.0.z) Timer fails if transaction isolation set to SERIALIZABLE
- Closed