David, It is possible to configure CAS for HA without Tomcat session replication. This is done by configuring CAS to use the Spring Web Flow Client Continuation Flow Execution Repository. This basically stores all information necessary to relay a conversation in the form the user receives, which was previously replicated via Tomcat session replication.
http://static.springframework.org/spring-webflow/docs/1.0.x/reference/flow-e xecution-repository.html#repository-client You can enable this by setting the "repository-type" attribute of the "flow:executor" element within cas-servlet.xml to "client" like so: <flow:executor id="flowExecutor" registry-ref="flowRegistry" repository-type="client"> Once you do this on all of your CAS deployments, you should be able to disable Tomcat session replication. HTH, A- On 3/19/09 12:08 AM, "David Ruwoldt" <[email protected]> wrote: > Dear All, > > Sorry for all the questions. > > CAS 3.3.1, RHEL 5.3, Tomcat 5 > > We have seen the following exception twice in the last 18 hours. > > Exception in thread "org.apache.catalina.cluster.tcp.TcpReplicationThread[4]" > java.lang.OutOfMemoryError: Java heap space > > The node becomes unresponsive and the cluster goes down because the load gets > transferred > to the other node which then runs out of memory. > > We have only been running with 1 GB of ram on the VM's. We are changing this > to 4 GB of > ram tonight. We are also setting the tomcat param -Xmx to 3 GB. > > Is there anything else we should be looking at. I have downloaded a heap of > tomcat tuning > doco but have not had time to read it as yet. > > Yours sincerely > > David Ruwoldt -- Andrew Feller, Analyst LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
