[jboss-jira] [JBoss JIRA] (WFLY-5051) Requests for persistent sessions always trigger replication

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-5051:
-------------------------------
    Description: 
For persistent sessions, we trigger session session activation events after a successful SessionManager.findSession(...).  However, this is currently triggered using a Session instance, instead of an ImmutableSession instance, which causes iteration over session attributes to trigger replication of the session at the end of the request - even when the user does not access any mutable session attributes.

The same is true for Session.close() (via session passivation event).

  was:For persistent sessions, we trigger session session activation events after a successful SessionManager.findSession(...).  However, this is currently triggered using a Session instance, instead of an ImmutableSession instance, which causes iteration over session attributes to trigger replication of the session at the end of the request - even when the user does not access any mutable session attributes.



> Requests for persistent sessions always trigger replication
> -----------------------------------------------------------
>
>                 Key: WFLY-5051
>                 URL: https://issues.jboss.org/browse/WFLY-5051
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.Alpha6
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>
> For persistent sessions, we trigger session session activation events after a successful SessionManager.findSession(...).  However, this is currently triggered using a Session instance, instead of an ImmutableSession instance, which causes iteration over session attributes to trigger replication of the session at the end of the request - even when the user does not access any mutable session attributes.
> The same is true for Session.close() (via session passivation event).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)