I have 2 Tomcats (both 5.0.19) running on two separate machines. One machine also has Apache 2.0.49 installed on it for load balancing. Apache communicates with tomcat1 thru port 11005 and tomcat2 thru 12005. tomcat1 and Apache are on the same machine. Apache is set to forward /* to the load balancer (and then to Tomcats). We have over a hundred virtual hosts on our tomcats, so we don't want to worry about configuring Apache virtual hosts to serve the images and all the other files (that's why we forward /*, not just /*.jsp and /servlet/*). Both tomcats also have their http connector ports listening to port 8080 on their individual machines. We're using mod_jk_1.2.5_2.0.47.dll for Apache to Tomcat communication... Both our tomcats are running with the -Xms128m -Xmx256m options.
With this configuration everything works perfect for about an hour, then our tomcats run out of memory...
When we turn off clustering, and run a single Tomcat on port 80 (of course by shutting down Apache Httpd), we don't have any memory problems at all (for now, we're planning to use clustering to avoid down time, one server is actually enough to handle all the traffic).
Does anyone have any idea why we'd run out of memory when our tomcats are talking to Apache through mod_jk?
Thanks,
Asim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
