tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50189] New: AJP connector sends GET BODY CHUNK when reading after response closed
Date Mon, 01 Nov 2010 03:27:06 GMT

           Summary: AJP connector sends GET BODY CHUNK when reading after
                    response closed
           Product: Tomcat 5
           Version: 5.5.23
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connector:AJP

If a servlet (probably incorrectly) closes the writer/outputstream of a
response, and then attempts to read from the request, the AJP connector sends
GET BODY CHUNK to the mod_jk worker.

This then starts a series of very confusing communication between the worker
and tomcat.  The worker doesn't read it until it makes its next request.  After
making its next request, it reads it, and then sends a response with 0 length. 
At the same time, Tomcat responds to the request made by the worker with
another GET BODY CHUNK, which the worker also responds with a message of 0
length.  Then the really weird thing happens, Tomcat replays the first request
made by that worker.  At this point, based on what I'm looking at with tcpdump,
I get too confused to work out exactly what is happening.

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