[jboss-jira] [JBoss JIRA] (WFLY-9239) [GSS](7.1.0) Timer fails if transaction isolation set to SERIALIZABLE

[Stuart Douglas (JIRA)]

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

Stuart Douglas moved JBEAP-12775 to WFLY-9239:
----------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-9239  (was: JBEAP-12775)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: EJB
                           (was: EJB)
    Affects Version/s:     (was: 7.0.0.GA)
                           (was: 7.0.1.GA)
                           (was: 7.0.2.GA)
                           (was: 7.0.3.GA)


> [GSS](7.1.0) Timer fails if transaction isolation set to SERIALIZABLE
> ---------------------------------------------------------------------
>
>                 Key: WFLY-9239
>                 URL: https://issues.jboss.org/browse/WFLY-9239
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>         Environment: Linux, JDK8, Timer Database persistence
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>            Priority: Blocker
>              Labels: downstream_dependency
>
> 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)