[jboss-jira] [JBoss JIRA] Commented: (JBAS-5778) Improve HttpSessionListener handling in clustered environment

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on JBAS-5778:
----------------------------------------

This is done in Branch_4_2. Completion in trunk depends on getting jboss-metadata 1.0.0.CR2 or later integrated so JBMETA-120 can be picked up; then some minor changes in the tomcat module can be done to allow driving the notification policy via jboss-web.xml.

> Improve HttpSessionListener handling in clustered environment
> -------------------------------------------------------------
>
>                 Key: JBAS-5778
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5778
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA, JBossAS-4.2.1.GA, JBossAS-4.2.2.GA, JBossAS-4.2.3.GA
>            Reporter: Takayoshi Kimura
>            Assignee: Brian Stansberry
>
> Suppose we have a web application which uses stateful session beans, and we have a HttpSessionListener like this:
> public void sessionDestroyed(HttpSessionEvent event) {
>     event.getSession().getAttribute("sfsb").remove(); // Make sure to call SFSB's @Remove method
> }
> This behavior is what Seam does.
> The HttpSessionListener.sessionDestroyed() would be called in session invalidation, session timeout and during undeploy/shutdown for cleaning up local resources. This happens in both cases, clustered and non-clustered .
> However, in clustered environment, the sfsb.remove() method call in HttpSessionListener becomes a cluster-wide operation. So when we shutdown one node, HttpSession is still available on the other node for fail over but SFSB is missing. As a result we will get javax.ejb.NoSuchEJBException: Could not find stateful bean.

-- 
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