[
https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin...
]
Paul Ferraro commented on WFLY-12653:
-------------------------------------
[~brian.stansberry] Honestly, it should probably have been filed as critical. If
you're ok with it going into 18.0.1, I would say yes.
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
Labels: downstream_dependency
Fix For: 19.0.0.Beta1
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)