[jboss-jira] [JBoss JIRA] (WFLY-6412) Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g

Gábor Péntek (JIRA) issues at jboss.org
Wed Apr 27 08:43:00 EDT 2016


     [ https://issues.jboss.org/browse/WFLY-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gábor Péntek updated WFLY-6412:
-------------------------------
        Fix Version/s:     (was: 8.2.0.Final)
                           (was: 10.0.0.Final)
    Affects Version/s: 10.0.0.Final
                       8.2.0.Final


> Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g
> ----------------------------------------------------------------------
>
>                 Key: WFLY-6412
>                 URL: https://issues.jboss.org/browse/WFLY-6412
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 8.2.0.Final, 10.0.0.Final
>         Environment: Linux, JDK8, Oracle DB 11g
>            Reporter: Gábor Péntek
>
> 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
(v6.4.11#64026)



More information about the jboss-jira mailing list