Java EE (Java Enterprise Edition) General Discussion

Hello,

Per a previous disscussion thread I am using JSF client state-saving to save the client session data, and when a failover occurs in a clustered environment the JSF true should be available on the recovering server. I am speculating that the JSF server pulls the JSF component tree from a hidden field in the browser web page. This seemed to work doing a simple test but now that I am capturing more complete data that is saved in a Java Bean (Managed Bean) it seems to be failing as the managed bean is empty on the recovering server (server 2 in a cluster of 2 JBoss 3.2.4/Tomcat.50 app Servers). Is it possible that a new instance of the managedBean is being created because the original managed bean is not be stored in the client page as part of the JSF tree? How can I really confirm that client state-savings actually works in a clustered environment???

Thanks of any help.