The amount of session replication data that moves back and forth will depend on the replication configuration (SYNC/ASYNC/Interval etc.) and the amount of data that gets changed and how offen.
We deployed an app in a cluster of three servers using SYNC and a legacy architecture that required a large amount of session state in the HTTP session. We were able to significantly reduce the payload size of the transfers by making all the session resident objects externalizable and hand coding the serlialization. It's quite a bit of work but it paid off. Based on the invocation statistics in the web console, the ClusteredHttpSession EJB had averages of no more than 1 ms. for any method, so we're happy with it. (And unfortunately/fortunately, we have had a few production occurences where we were able to verify that it worked first hand........:) ) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847207#3847207 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847207 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
