This is the same bug as the memory leak bug that has been going on and on
and on and on this list ;-). The fix is the same:
1) Use the work-around of setting 'request.registerRequests=false' in
jk2.properties.
2) Upgrade to 5.0.20+
Allistair Crossley [EMAIL PROTECTED] wrote in message
Hi All,
This is a repost of an issue we are still experiencing on the production server. I
found a similar post re: tomcat 4 that was a bug (although cannot find in bugzilla
now). The same thing happens to us ..
I have been looking through our production server logs and the following error
