[JBoss JIRA] (WFLY-13639) Avoid duplicate expiration scheduling on member leave for non-tx invalidation cache
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13639?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13639:
--------------------------------
Description: Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs. (was: Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs.
By storing the address of the member that handled a given request along with a web session/SFSBs metadata, we can discriminate which entries require expiration rescheduling on topology change for non-tx invalidation caches.)
> Avoid duplicate expiration scheduling on member leave for non-tx invalidation cache
> -----------------------------------------------------------------------------------
>
> Key: WFLY-13639
> URL: https://issues.redhat.com/browse/WFLY-13639
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Following WFLY-13627, a non-tx invalidation cache will schedule session/SFSB expiration on the local member. When that member leaves, the expiration will be reschedule on the primary owner of segment 0 (in a non-tx cache, all entries map to segment 0). However, since that member cannot distinguish which sessions/SFSBs were owned by the leaving member, it must schedule all sessions/SFSBs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-5034) Upgrade log4j to 2.13.3
by Jeff Mesnil (Jira)
Jeff Mesnil created WFCORE-5034:
-----------------------------------
Summary: Upgrade log4j to 2.13.3
Key: WFCORE-5034
URL: https://issues.redhat.com/browse/WFCORE-5034
Project: WildFly Core
Issue Type: Feature Request
Components: Test Suite
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
The embedded test suite uses Log4J 2.11.0 when its tests are run.
The version should be upgrade to 2.13.3
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ELY-2007) Add SecurityIdentity PolicyContextHandler
by Darran Lofthouse (Jira)
Darran Lofthouse created ELY-2007:
-------------------------------------
Summary: Add SecurityIdentity PolicyContextHandler
Key: ELY-2007
URL: https://issues.redhat.com/browse/ELY-2007
Project: WildFly Elytron
Issue Type: Enhancement
Components: EE
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.13.0.CR2
There is an implementation in WildFly Core but really the implementation is not specific to the integration in the application server so it should be moved into the WildFly Elytron project.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ELY-2006) Add a "Delegating" PolicyContextHandler
by Darran Lofthouse (Jira)
Darran Lofthouse created ELY-2006:
-------------------------------------
Summary: Add a "Delegating" PolicyContextHandler
Key: ELY-2006
URL: https://issues.redhat.com/browse/ELY-2006
Project: WildFly Elytron
Issue Type: Enhancement
Components: EE
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.13.0.CR2
We have some cases in WildFly Core where we need to install a WildFly Elytron PolicyContextHandler but delegate to a legacy implementation if an Elytron identity is not available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years