[jboss-jira] [JBoss JIRA] (WFLY-8043) Timer fails if transaction isolation set to SERIALIZABLE
Wolf-Dieter Fink (JIRA)
issues at jboss.org
Tue Feb 7 07:03:00 EST 2017
[ https://issues.jboss.org/browse/WFLY-8043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wolf-Dieter Fink updated WFLY-8043:
-----------------------------------
Summary: Timer fails if transaction isolation set to SERIALIZABLE (was: Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g)
> Timer fails if transaction isolation set to SERIALIZABLE
> --------------------------------------------------------
>
> Key: WFLY-8043
> URL: https://issues.jboss.org/browse/WFLY-8043
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.0.Final, 10.0.0.Final
> Environment: Linux, JDK8, Oracle DB 11g
> Reporter: Wolf-Dieter Fink
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list