Hi, Does the memory leak occur when you run tomcat standalone?
I can't run the production server in standalone, and I can't seem to hit my test server hard enough to reproduce the problem clearly. I'll keep trying.
Can you
point out its source e.g. by running with a profiler?
I don't have a profiler :(
Was the load
during these 50 minutes exceptionally heavy?On the heavy side, but not really stressing the server except for this memroy leak. Tomcat 4.1.18 handled loads like this all the time.
BTW How can I view the jk2 status? I tried both of these: In httpd.conf: <Location "/jkstatus/*"> JkUriSet worker status </Location>
in workers2.properties: [uri:/status/*] worker=status:status
In my error_log I see:
[Wed Mar 17 14:26:42 2004] [notice] Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7a mod_jk2/2.0.2 configured -- resuming normal operations
[Wed Mar 17 14:26:42 2004] [error] uriEnv.init() map to invalid worker /jkstatus/* status
[Wed Mar 17 14:26:42 2004] [error] uriEnv.init() map to invalid worker /status/* status:status
[Wed Mar 17 14:26:42 2004] [error] mod_jk child init 1 -2
[Wed Mar 17 14:26:43 2004] [error] jk2_init() Can't find child 2506 in scoreboard
... and going to the url just produces a 500 error.
Also The faq at http://jakarta.apache.org/tomcat/faq/connectors.html says that mod_jk is the preferred connector and that jk2 is not production quality. My understanding was that jk was in maintence mode and jk2 is considered the stable connector. Is the faq right or is it just out of date?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
