[ https://issues.jboss.org/browse/WFLY-5051?page=com.atlassian.jira.plugin.... ] 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)