Jetty

The AJP13 protocol implementation seems to not like large packets of data, perhaps with lots of XML in t hem? repeatable problem

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 6.1.2rc0
  • Fix Version/s: 6.1.2rc0
  • Component/s: None
  • Labels:
    None
  • Environment:
    SuSE 10.1 against mod_proxy_ajp running on Apache 2.2
  • Number of attachments :
    2

Description

When posting back a form with a lot of data, large portions of the data don't come through. The same form using the SelectConnector works perfectly under all situations. When using the AJP13 connector it always fails - large parts of the data appears to be missing.

  1. File
    bad_ajp.dmp
    13/Feb/07 1:10 AM
    33 kB
    Richard Vowles
  2. File
    bad_ajp2.dmp
    14/Feb/07 2:38 AM
    32 kB
    Richard Vowles

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Greg Wilkins added a comment -

I believe that this issue may also be fixed with the work done on JETTY-237 plus a change I made to the buffer full test.

checked into SVN now.

Please test and confirm

Show
Greg Wilkins added a comment - I believe that this issue may also be fixed with the work done on JETTY-237 plus a change I made to the buffer full test. checked into SVN now. Please test and confirm
Hide
Permalink
Richard Vowles added a comment -

tcpdump of the port traffic after updating the jetty to the SVN head and rebuilding from scratch and redeploying. Still fails repeatably.

Show
Richard Vowles added a comment - tcpdump of the port traffic after updating the jetty to the SVN head and rebuilding from scratch and redeploying. Still fails repeatably.
Hide
Permalink
Greg Wilkins added a comment -

Richard,

thanks for the dump. However it looks good to me!

I can see Jetty requesting 12 chunks of request content and all 12 are sent and then the response is completed. I can see all 23748 bytes of content sent.

The only strange thing is that I see the response headers are sent after 2758 bytes (in 2 chunks).
So I think the actual AJP connector is working, but something higher up the food chain is failing.

How are you handling this request? What is decoding the content? Jetty or are you doing that yourself?

Show
Greg Wilkins added a comment - Richard, thanks for the dump. However it looks good to me! I can see Jetty requesting 12 chunks of request content and all 12 are sent and then the response is completed. I can see all 23748 bytes of content sent. The only strange thing is that I see the response headers are sent after 2758 bytes (in 2 chunks). So I think the actual AJP connector is working, but something higher up the food chain is failing. How are you handling this request? What is decoding the content? Jetty or are you doing that yourself?
Hide
Permalink
Greg Wilkins added a comment -

OK 99.999999% I have fixed it this time.

I actually reproduced it and then fixed it!

An EOF was wrongly being returned on some chunk boundaries.

Show
Greg Wilkins added a comment - OK 99.999999% I have fixed it this time. I actually reproduced it and then fixed it! An EOF was wrongly being returned on some chunk boundaries.

People

  • Assignee:
    Greg Wilkins
    Reporter:
    Richard Vowles
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
1w
Original Estimate - 1 week
Remaining:
1w
Remaining Estimate - 1 week
Logged:
Not Specified
Time Spent - Not Specified