]
Brian Stansberry updated WFLY-12729:
------------------------------------
Fix Version/s: 18.0.1.Final
(was: 19.0.0.Beta1)
[18.0.x] Session passivation event can deadlock if it attempts write
operations on a session
--------------------------------------------------------------------------------------------
Key: WFLY-12729
URL:
https://issues.jboss.org/browse/WFLY-12729
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
Labels: downstream_dependency
Fix For: 18.0.1.Final
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.