[
https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi...
]
Paul Ferraro updated WFLY-13627:
--------------------------------
Description:
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the
session. For non-transactional invalidation caches expiration should always be scheduled
locally. This used to be the case, however, the logic for determining this has changed
such that expirations happen on the owner of segment 0.
This has the consequence of an RPC cost per request (and one after).
was:Currently, distributed web sessions (and SFSBs) are expired on the primary owner of
the session. For non-transactional invalidation caches expiration should always be
scheduled locally. This used to be the case, however, the logic for determining this has
changed such that expirations happen on the owner of segment 0.
Distributed sessions/SFSBs stored in non-transactional
invalidation-cache should schedule expirations locally
-------------------------------------------------------------------------------------------------------------
Key: WFLY-13627
URL:
https://issues.redhat.com/browse/WFLY-13627
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the
session. For non-transactional invalidation caches expiration should always be scheduled
locally. This used to be the case, however, the logic for determining this has changed
such that expirations happen on the owner of segment 0.
This has the consequence of an RPC cost per request (and one after).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)