Ok, I'm wrong, passivation of a clustered web app doesnt' work! But the cluster-cache behavior is different from 4.0.1 to 4.0.3. * 4.0.1: When restarting/redeploying webapps, the session is still valid in cluster cache. Customers can finish their work without problems. * 4.0.3: Session is lost after restart/redeploy
I've found one important difference between 4.0.1 and 4.0.3. * 4.0.1 stores the session in cluster cache in path /JSESSION. * 4.0.3 in path /JSESSION/localhost/context I think, if context is stopped or removed on 4.0.3, the session is also removed. But only on one node! 4.0.1 doesn't remove the session. If I stop the application on only one(!) node and printDetails from TomcatClusterCache JMX-bean, the session was removed only on this node. printDetails on the other nodes with running webapps still find the session. Now if I start the webapp on the first node again, my cluster session is gone and a new version is started and replicated in cluster cache. Btw: I've written a simple test-servlet that counts each request and stores the counter in http-session. Try to restart such a servlet (all nodes) in cluster environment. 4.0.1 works. 4.0.3 not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922836#3922836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922836 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
