Hi,
we had the same problem (enormous memory leak which frequently made our production system crash), downgraded to 5.0.18 and everything went back to normal. Just yesterday a colleague of mine came to the conclusion that it is not too unlikely that it is the problem described in the message
http://www.mail-archive.com/[EMAIL PROTECTED]/msg53035.html
It that is so, you can simply disable the JMX registration of requests to get rid of the problem. We will try that probably later today but of course you can give it a shot yourself. There is not much to lose.
I was able to figure out how to reproduce this problem on my test machine (using multiple concurrent requests).
I added to my jk2.properties:
request.registerRequests=false
This got rid of some of the messages in catalina.out but left these:
Mar 19, 2004 1:47:51 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 Mar 19, 2004 1:47:52 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0
... and the memory leak did not go away.
The message that I'm not getting anymore are:
Mar 19, 2004 1:25:34 PM org.apache.jk.common.HandlerRequest decodeRequest WARNING: Error registering request Mar 19, 2004 1:25:34 PM org.apache.jk.common.HandlerRequest decodeRequest WARNING: Error registering request
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
