Re: AJP/Java connector issues

2005-05-20 Thread jean-frederic clere
Mladen Turk wrote: Hi, Just noticed a strange behavior in the Java part of the JK dealing with large (over 8184 bytes) data transfers. Since with 8192 bytes AJP packet size, the maximum transferred size per each packet is 8184 bytes one would expect that for 2 bytes file the packets would be

Re: AJP/Java connector issues

2005-05-20 Thread Bill Barker
- Original Message - From: jean-frederic clere [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Sent: Friday, May 20, 2005 9:02 AM Subject: Re: AJP/Java connector issues Mladen Turk wrote: Hi, Just noticed a strange behavior in the Java part of the JK

AJP/Java connector issues

2005-05-19 Thread Mladen Turk
Hi, Just noticed a strange behavior in the Java part of the JK dealing with large (over 8184 bytes) data transfers. Since with 8192 bytes AJP packet size, the maximum transferred size per each packet is 8184 bytes one would expect that for 2 bytes file the packets would be in a form of:

Re: AJP/Java connector issues

2005-05-19 Thread jean-frederic clere
Mladen Turk wrote: Hi, Just noticed a strange behavior in the Java part of the JK dealing with large (over 8184 bytes) data transfers. Since with 8192 bytes AJP packet size, the maximum transferred size per each packet is 8184 bytes one would expect that for 2 bytes file the packets would be

Re: AJP/Java connector issues

2005-05-19 Thread jean-frederic clere
Mladen Turk wrote: Hi, Just noticed a strange behavior in the Java part of the JK dealing with large (over 8184 bytes) data transfers. Since with 8192 bytes AJP packet size, the maximum transferred size per each packet is 8184 bytes one would expect that for 2 bytes file the packets would be

Re: AJP/Java connector issues

2005-05-19 Thread Bill Barker
- Original Message - From: Mladen Turk [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Cc: Bill Barker [EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 11:44 PM Subject: AJP/Java connector issues Hi, Just noticed a strange behavior in the Java part of the JK

Re: AJP/Java connector issues

2005-05-19 Thread Bill Barker
- Original Message - From: Mladen Turk [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Cc: Bill Barker [EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 11:44 PM Subject: AJP/Java connector issues Hi, Just noticed a strange behavior in the Java part of the JK

Re: AJP/Java connector issues

2005-05-19 Thread Mladen Turk
Bill Barker wrote: I see what this is now: The default Connector OutputBuffer size is 8K, so it's sending the output to JkInputStream in 8K chunks. JkInputStream sends all of the 8K to Apache in two chunks. As a Coyote OutputBuffer, it's not really JkInputStream's job to do additional

Re: AJP/Java connector issues

2005-05-19 Thread Bill Barker
- Original Message - From: Mladen Turk [EMAIL PROTECTED] To: Tomcat Developers List tomcat-dev@jakarta.apache.org Sent: Thursday, May 19, 2005 2:19 PM Subject: Re: AJP/Java connector issues Bill Barker wrote: I see what this is now: The default Connector OutputBuffer size is 8K

Re: AJP/Java connector issues

2005-05-19 Thread Mladen Turk
Bill Barker wrote: Is something like that possible? It would be really easy to default to 8184 for all Connectors (just change the value in o.a.c.connector.OutputBuffer). I'm not so sure how happy that would make Remy. Not much I'm afraid ;) It wouldn't be too hard to have

Re: AJP/Java connector issues

2005-05-19 Thread Remy Maucherat
Mladen Turk wrote: Bill Barker wrote: Is something like that possible? It would be really easy to default to 8184 for all Connectors (just change the value in o.a.c.connector.OutputBuffer). I'm not so sure how happy that would make Remy. Not much I'm afraid ;) It wouldn't be too hard to have