[jboss-jira] [JBoss JIRA] Commented: (JBAS-5819) Don't call expire when processing remote invalidation of clustered session

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12525187#action_12525187 ] 

Brian Stansberry commented on JBAS-5819:
----------------------------------------

The previous comment isn't a flaw in the approach described in this JIRA description per se. It's more that that approach is relying on flawed behavior. 

> Don't call expire when processing remote invalidation of clustered session
> --------------------------------------------------------------------------
>
>                 Key: JBAS-5819
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M3
>
>
> When JBC notifies JBossCacheManager that the root node for a session has been invalidated via a remote call, JBMC.processRemoteInvalidation() calls Session.expire on the local session (if there is one).  The expire call includes flags that result in no notifications being sent to any listeners.
> I don't see any point to this expire call if there are no notifications. The other work expire does is removing content from JBC, but the remote invalidation that triggers all this is already removing that content. Just drop the session from the local session map.  Perhaps flag the session so if there is a concurrency/sticky-session problem and a local request thread is handling the session it knows the session is invalid.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira