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

[Takayoshi Kimura (JIRA)]

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.3.GA, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.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