I finally got some time to look at this and I think I can duplicate the
problem your seeing. Hopefully, its the problem your seeing, or else we
have two serious problems.
I'm running Apache 1.3.9 (I'm too lazy to update) and mod_jk using AJP12 on
Win2000. I'm testing with
http://localhost:8081/examples/jsp/dates/date.jsp.
If I use JMeter to hit this URL on a single thread it works fine. As soon
as I start more than one thread the requests start to hang. I can also
duplicate the problem by hitting the same URL from two machines and then
holding down the F5 key on both browsers. Things get stuck, but after some
time the requests seem to become unstuck and things start working again.
I'm not sure how much time I'm going to have to investigate the problem this
weekend (my honey-do list is pretty long), but I'll be looking hard at it on
Monday. This is a show stopper bug for 3.2.2.
> -----Original Message-----
> From: Pogo Com [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 19, 2001 7:19 PM
> To: [EMAIL PROTECTED]
> Subject: 3.2.2b3 mod_jk gets stuck in readFully
>
>
> I've been testing Tomcat 3.2.2b3 and Apache 1.3 on Solaris, connected with
> mod_jk. Things are generally working, but there is a serious problem that
> occurs under load.
>
> The problem is that certain Apache children get stuck talking to
> Tomcat. The
> children are always requesting JSP pages. Using the Apache
> status display, a
> stuck child looks like:
>
> 141-0 29388 0/1/1 W 0.00 1092 0 0.0 0.01 0.01 154.x.x.x
> bingoe01.mysite.com
> GET /ad/loading-applet.jsp?tabl=1&site=pogo&scrn=motormind&anam
>
> It is not uncommon to have half of the Apache children stuck like
> this. On
> the tomcat side, the threads appear at this location:
>
> "Thread-256" (TID:0xd020a0, sys_thread_t:0xd01fd8, state:R,
> thread_t: t@263,
> threadID:0x63cb1dd8, stack_bottom:0x63cb2000, stack_si
> ze:0x20000) prio=5
>
> [1] java.net.SocketInputStream.socketRead(Native Method)
> [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
> [3]
> org.apache.tomcat.service.connector.TcpConnector.receiveFully(TcpC
> onnector.java:148)
> [4]
> org.apache.tomcat.service.connector.TcpConnector.receive(TcpConnec
> tor.java:118)
> [5]
> org.apache.tomcat.service.connector.Ajp13ConnectionHandler.process
> Connection(Ajp13ConnectionHandler.java:109)
> [6]
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:393)
> [7]
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:475)
> [8] java.lang.Thread.run(Thread.java:478)
>
> Generally, the number of threads inside receiveFully matches the number of
> stuck Apache children.
>
> Losing Apache children like this eventually starves the server of
> ability to
> do useful work, even though there is a lot of idle time on the
> machine. Is
> this a known issue?
>
> Thanks,
> Bill Lipa
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
