tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <bo...@binarix.com>
Subject mod_jk 1.2.0/1.1.0 vs ab
Date Fri, 05 Oct 2001 02:51:27 GMT
Just for fun I did this to exercise mod_jk/TC 3.3 combination:

---------------------------------------
ab -c 1 -n 1000 http://some/velocity/page.vm
---------------------------------------

This goes OK on both 1.1.0 and 1.2.0, although some requests aren't
served (probably because no more threads are available in ajp13
connector - I run a max of 50).

However, if I attempt this:

---------------------------------------
ab -c 5 -n 1000 http://some/velocity/page.vm
---------------------------------------

with mod_jk 1.1.0 or:

---------------------------------------
ab -c 20 -n 1000 http://some/velocity/page.vm
---------------------------------------

with mod_jk 1.2.0, I eventually get this in the log files:

---------------------------------------
2001-10-05 13:34:58 - Ajp13Interceptor: Processing connection
org.apache.tomcat.
        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:
        at
org.apache.tomcat.modules.server.Ajp13Request.receiveNextRequest(Ajp1
        at
org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(A
        at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
        at java.lang.Thread.run(Thread.java:484)
---------------------------------------

Both TC and mod_jk stay up, so I'm guessing this is normal?

Bojan

Mime
View raw message