DO NOT REPLY [Bug 46623] New: Tomcat/IIS closes socket after http response has completed

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=46623

           Summary: Tomcat/IIS closes socket after http response has
                    completed
           Product: Tomcat Connectors
           Version: 1.2.27
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: major
          Priority: P2
         Component: isapi
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: kpectbi@gmail.com


Created an attachment (id=23189)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?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 workers.properties file of the connector:

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 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: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

DO NOT REPLY [Bug 46623] Tomcat/IIS closes socket after http response has completed

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=46623


Tim Whittington <Ti...@orionhealth.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Tim Whittington <Ti...@orionhealth.com>  2009-01-29 02:01:00 PST ---
Up until 1.2.27 this was the behaviour of the IIS connector (IIS forces all
ISAPI extensions to implement their own HTTP keep alive, and the IIS connector
didn't do this).

In 1.2.27 there's experimental, build-time, support for HTTP 1.1 chunked
encoding, which should permit persistent connections.
(I've been using pretty much the same code in production systems for about 4
years, but it should be considered experimental in the JK codebase until it's
been stable for a while).

Grab the -chunked binary from one of the download mirrors and read about how to
configure chunked encoding in the 1.2.27 release notes (you have to get the
right build, and enable it in your config).
You can verify that the connector is using chunked encoding with debug logging
on, and a TCP/Wireshark trace should show connections being reused.

If you're still getting closed connections, and the logs show that the
connector is attempting (or should be attempting) chunked encoding, then it's
probably best to discuss on the users list and then reopen with another
Wireshark trace + connector debug log once you're sure there's an issue.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org