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
news:[E
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 blo
Hi All,
I have been looking through our production server logs and the following error block
is repeated an awful lot, like every 6 minutes or so and sometimes 6 times per minute.
06-May-2004 14:38:50 org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
java.net.SocketExcept
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:479)
[ERROR] JkCoyoteHa