java - Tomcat/IIS closes socket after http response has completed -

I am using Jebos 4.0.4 Ge, which contains Tomé Service Service Container 5.5. I have been redirected to IIS 6.0 at this jobbase. (Via the IIS tomcat connector, which is used as an ISAPI filter in IIS). .

  # # Defines a worker named ajp13 and configured for the described workers as is all working fine,  
 Here connector workers.properties file One piece is type ajp13 # Note that the name and type is not to match. # Worker.jboss0_ajp13.port = 8009 worker.jboss0_ajp13.type = ajp13 worker.jboss0_ajp13.host = localhost worker.jboss0_ajp13.socket_keepalive = 1 worker.jboss0_ajp13.socket_timeout = 300  

But when For application through connecting IIS (Port 80), for every complete HTTP response for the HTTP request, the socket is off (the FIN is sent on the TCP layer) because it is a serious recession, because the application is working on WAN is. (For each closed socket, one must be installed, which takes 500 mms).

It JBoss is not connected directly to the web server, and can not be connected to the virtual directory on another IIS same webserver Keep-Alive in instanse (ie IIS's Is configured).

This badge happens with the latest version of the IIS connector.

Do you know if there is a bug in the connector, or is there a problem in my configuration?

Thanks in advance, Henry.

I've filed a bug for Tomcat IIS redirectors in Bugzilla, and it is an answer to me :

up until 1.2.27 this was IIS connector behavior (IIS keeps alive all its Aispiai extension to implement its Aispiai extension, and not the IIS connector Done).

experimental 1.2.27, Build-time, HTTP 1.1 support for Chanked encoding, which perm must persistent connections (I'm pretty much in production systems for almost 4 years I am using the same code, but it should be considered experimental in the JK codebase, until it is not stable for a while).

Hold the spry binary from one of the download mirrors and read about how to configure encoded encoding in 1.2.27 release notes (you have to get the right build , And have to enable it in its config). You can verify that the chunked encoding with the connector debug entry is used, and a TCP / Wireshark trace should show that connection is being reused.

You are still getting closed connections, and the log suggests that the connector is trying (or trying should be attempted) chunked encoding, so it probably To discuss those lists and then explore another Wireshark + reopen with the connector debug logs once you are sure you have a problem is best.

So, what I did.

1. Put the isapi_redirect.dll with support idle

2. isapi_redirect property with the following:

   enable_chunked_encoding = 1

3. Restart IIS