tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46623] New: Tomcat/IIS closes socket after http response has completed
Date Thu, 29 Jan 2009 09:22:42 GMT

           Summary: Tomcat/IIS closes socket after http response has
           Product: Tomcat Connectors
           Version: 1.2.27
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: major
          Priority: P2
         Component: isapi

Created an attachment (id=23189)
 --> (
WireShark response description, when connecting directly to JBoss and via IIS

I am using JBoss 4.0.2, which has Tomcat Servlet Container 5.5.
I also have IIS 6.0 redirected to this JBoss. (via IIS tomcat connector, which
is used as ISAPI filter in IIS). All is working OK, configured the workers as
described in documentation.

Here is a piece of file of the connector:


But when connecting to the application via IIS (port 80), for each completed
HTTP response for HTTP request, the socket is closed (FIN is sent on the TCP
layer and "Connection: close" is sent on the HTTP layer). This causes severe
slowdowns, since the application is working over WAN. (for each closed socket,
another one needed to be established, which takes 500ms).

This is not happening when connecting to JBoss web server directly, and also
not happening when connecting to a different virtual directory on the same
WebSite of IIS (i.e. Keep-Alive in IIS is also configured).

This happens with the latest version of tomcat IIS connector (1.2.27).

Attaching WireShark description of the response w/wo IIS redirection.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message