You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Michael Reardon <mi...@contrafactus.com> on 2002/09/09 18:23:31 UTC

AJP13 and bug 10383

Hi,
I could really use some recommendations. I'm having a problem with the
AJP13 processors locking up Tomcat. My problem sounds very much like bug
10383... http://issues.apache.org/bugzilla/show_bug.cgi?id=10383

The configuration is Tomcat 4.0.4, Windows 2000, IIS 5, ISAPI Redirect
and AJP 13 from the jakarta-tomcat-4.0.4.exe distribution (which appears
to be the same as distributed with Tomcat 3.3).

The catalina_log file shows that the management of Ajp13Processors seems
to spin out of control, incrementally starting processors in a loop,
starting 70 processors in under 3 seconds. Once the number of processors
reachs the maximum (I have it set for 150), the Ajp13Connector starts
rejecting all connections.

2002-09-04 13:31:09 Ajp13Processor[8009][116] Starting background thread

2002-09-04 13:31:10 Ajp13Processor[8009][117] Starting background thread

... snip ...
2002-09-04 13:32:06 Ajp13Processor[8009][148] Starting background thread

2002-09-04 13:32:07 Ajp13Processor[8009][149] Starting background thread

2002-09-04 13:32:07 Ajp13Connector[8009] No processor available,
rejecting this connection
2002-09-04 13:32:08 Ajp13Connector[8009] No processor available,
rejecting this connection
2002-09-04 13:32:09 Ajp13Connector[8009] No processor available,
rejecting this connection
2002-09-04 13:32:09 Ajp13Connector[8009] No processor available,
rejecting this connection
... and so on, and so on ...

The only clue I have as to the cause, is a lot of  SocketExceptions from
connection resets. My understanding was that this was caused by users
stopping or closing browsers before a request is completed, and they are
safely ignored.

2002-09-04 12:29:37 Ajp13Processor[8009][18] process: invoke
java.net.SocketException: Connection reset by peer: socket write error
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 at org.apache.ajp.Ajp13.send(Ajp13.java:525)
 at org.apache.ajp.RequestHandler.finish(RequestHandler.java:495)
 at org.apache.ajp.Ajp13.finish(Ajp13.java:395)
 at
org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196)

 at
org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464)
 at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
 at java.lang.Thread.run(Thread.java:484)

The only other unusual activity I can find is a number of servlet
exceptions thrown form one of my servlets, which prevents overly large
files from being submitted with a multipart mime request.

I need to use IIS and 2.3 servlets at this time, so I think my options
for connectors are limited. Any help or suggestions would be greatly
appreciated.

Thanks,
Mike Reardon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>