[jboss-jira] [JBoss JIRA] (WFLY-12653) Session passivation event can deadlock if it attempts write operations on a session

[Paul Ferraro (Jira)]

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

Paul Ferraro moved JBEAP-17759 to WFLY-12653:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-12653  (was: JBEAP-17759)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                           (was: Clustering)
    Affects Version/s: 18.0.0.Final
                           (was: 7.3.0.CD17)
                           (was: 7.2.4.GA)


> Session passivation event can deadlock if it attempts write operations on a session
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-12653
>                 URL: https://issues.jboss.org/browse/WFLY-12653
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 18.0.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Major
>
> Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes.
> In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..).  However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries.  This should never be done within the context of an activation/passivation event.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)