Bojan Smojver wrote:
> Since I can control the headers from my servlet, let my try with
> Content-length. Fingers crossed...
If think this can actually qualify as a bug in ab - even when I set
Content-Length header, it still says that that there are length
failures. Since jsessionid can sometimes have 10 and sometimes 11
characters and I use it on the page to encode the URL, sometimes the
pages are a byte longer...
But ab still takes into the account only the length of the very fist
page. Good news is that there is nothing wrong with TC.
Bojan
PS. What do you make of those stack traces? It looks as if mod_jk
dropped the connection and TC then goes into Exception...
-----------------------------------------------
2001-10-05 17:03:57 - Ajp13Interceptor: Processing connection
org.apache.tomcat.util.net.TcpConnection@5ec199 -
java.net.SocketException: Connection reset by peer: Connection reset by
peer
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at org.apache.tomcat.modules.server.Ajp13.readN(Ajp13.java:729)
at
org.apache.tomcat.modules.server.Ajp13.receive(Ajp13.java:763)
at
org.apache.tomcat.modules.server.Ajp13.receiveNextRequest(Ajp13.java:271)
at
org.apache.tomcat.modules.server.Ajp13Request.receiveNextRequest(Ajp13Interceptor.java:277)
at
org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(Ajp13Interceptor.java:192)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:477)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:517)
at java.lang.Thread.run(Thread.java:484
-----------------------------------------------
