We are trying to move our application into a clustered environment. During our
testing, we ran into a problem when the oc4j is taken down on server 1, the user is required to log back into the application on server 2. There is not a seamless transition. The application architecture is
JSP,
struts, and stateless session beans. According to the Oracle documentation, the only thing I had to do to make the application highly available is to add <distributable/> to web.xml. Is this right?
Also, we have a HttpSessionLister that listens for sessions being destroyed. I have noticed that the listener's sessionDestroyed() method is being fired when the oc4j is taken down. The sessionDestroyed() mehtod removes all session attributes when a session is destroyed. This would cause the user to have to login again on the clustered server since the user's credentials are removed. So my question is: Is the sessionDestroyed method supposed to fire when the oc4j is taken down in a clustered environment?
