David,It is worrisome to hear that Tomcat session replication may be causing the OutOfMemoryError. Well, it may not be the cause, but1 GB is a lot of memory for CAS.
Did you have a chance to try what Andrew suggested? His modification eliminates the need for Tomcat session replication, and if that was the cause of a memory leak, you would have effectively eliminated it.
Are you using the version of Tomcat that comes with RHEL 5.3 or a separate version directly from Apache? I ask because the version distributed with RHEL looks to be heavily modified from the original distribution and fairly old.
Adam David Ruwoldt 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 spaceThe 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
begin:vcard fn:Adam Rybicki n:Rybicki;Adam org:Unicon, Inc.;Professional Services adr:Suite 113;;3140 North Arizona Avenue;Chandler;AZ;85225;United States email;internet:[email protected] tel;work:+1-480-558-2400 tel;home:+1-310-265-8286 tel;cell:+1-310-980-2758 x-mozilla-html:FALSE url:http://www.unicon.net/ version:2.1 end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
