Our Tomcat 5.0.19 runs out of memory when load testing through an Apache 1.3.26 proxy, but does not when the the same load test accesses Tomcat's HTTP port directly. We initially saw the problem with mod_jk, but once we saw that Tomcat didn't run out of memory with direct HTTP access , we went for the proxy approach, since both direct and proxied accesses connect to Tomcat via HTTP. We configured Apache forward and reverse proxies according to http://jakarta.apache.org/tomcat/tomcat-5.0-doc/proxy-howto.html
We've seen the same problem with Tomcat 5.0.24, but have not tested it as extensively. Has anyone else seen Tomcat run out of memory when accessed through an Apache proxy, but not when it's accessed directly? If so, what did you do to remedy it? I welcome any reasonable suggestions. We want to keep Apache as our HTTP front end for now. Also, I ran direct and proxied tests with profiling (-Xrunhprof) on Tomcat, but don't see anything obvious from the metrics. I'll gladly provide both profile dumps to anyone who wants to take them on. Thanks. -- Richard Cunningham E-Mail: [EMAIL PROTECTED] Aircraft Shopper Online Web : http://www.ASO.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
