IIS JK connector issues with connections forcibly closed.

[IanC <ia...@raymondjames.com>]

Good afternoon,
I have a web service that is hosted on tomcat v4.  I use the jakarta
redirect DLL with IIS to "front-end" the requests.  Under load, I receive
quite a few exceptions from my client application consuming the web service.  
The exceptions are all the same and read: 
"System.IO.IOException: Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host."

My workers.properties for the ajp13 connector is setup like this:
worker.ajp13.port=8809
worker.ajp13.host=127.0.0.1
worker.ajp13.connection_pool_size=100
worker.ajp13.type=ajp13
worker.ajp13.lbfactor=1
worker.ajp13.cachesize=150
worker.ajp13.cache_timeout=600
worker.ajp13.recycle_timeout=300
worker.ajp13.socket_timeout=30
worker.ajp13.socket_keepalive=1

In my server.xml for tomcat I have:
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="8809" minProcessors="10" maxProcessors="150"
               enableLookups="false" redirectPort="8844"
               acceptCount="100" debug="0" connectionTimeout="20000"
               useURIValidationHack="false" address="127.0.0.1"
              
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>

I am able to put thru ~60 requests per second to give you an idea about load
and the client applcation runs 10 threads to generate the load.  Out of
about 6000 requests I get around 10 to 100 of these failures.  If I retry
the request, the subsequent request always succeeds so I am a little
puzzled.

I have done a few things to try and pinpoint the error:
1) Not using IIS and going to tomcat directly over the defined HTTP
connector works without error.
2) I receive the same error using the old AJP1.3 connector as I do with the
new coyote 1.3 connector.
3) I have tried setting timeouts higher on tomcat or higher on the jk isapi
redirect filter with no success.
4) Even debugging all components does not present an additional error.
5) I have been searching Google for the error and some other keywords like
"IIS" and "Tomcat" that have resulted in some good results but none that
seem to solve my issue.

If someone could point me in the right direction I would really appreciate
it.  This problem is going to drive me to drink! :)  What am I missing?

Thanks so much in advance for any assistance!

- Ian

-- 
View this message in context: http://www.nabble.com/IIS-JK-connector-issues-with-connections-forcibly-closed.-tf4118888.html#a11713813
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: IIS JK connector issues with connections forcibly closed.

[IanC <ia...@raymondjames.com>]

As an update, I did find that I was a few revs behind on the isapi connector
version.  I did upgrade but found that the error persists. :(
-- 
View this message in context: http://www.nabble.com/IIS-JK-connector-issues-with-connections-forcibly-closed.-tf4118888.html#a11715708
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org