RE: configurable AJP Buffer Size
-Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, April 06, 2006 12:57 AM To: Tomcat Developers List Subject: Re: configurable AJP Buffer Size Henri Gomez wrote: well client and server should be in phase about the buffer size and the better way to accomplish that will be via AJP13 extensions (ie AJP14), with connect time negociation datas like packet buffer size :) Right. Extensions could contain packet size. The problem is that even with the custom size that size would be limited to 32K, and again someone will complain about that limitation ;) Possible. But, I have no idea why connector should be constraining this. - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
Just take a look at the AJP protocol documentation : http://tomcat.apache.org/connectors-doc/common/ajpv13a.html Packets sent from the server to the container begin with 0x1234. Packets sent from the container to the server begin with AB (that's the ASCII code for A followed by the ASCII code for B). After those first two bytes, there is an integer (encoded as above) with the length of the payload. Although this might suggest that the maximum payload could be as large as 2^16, in fact, the code sets the maximum to be 8K. So to support more than 64k bytes, we should have a whole new code on Apache and Tomcat side and break compatibility with all current implementations. And that's bad ;( Take a look at the AJP13 extension proposal : http://tomcat.apache.org/connectors-doc/common/ajpv13ext.html We could plug many usefull informations in LOGIN INIT for example ! 2006/4/6, KARNATI, SRINIVASA R [AG/1000] [EMAIL PROTECTED]: -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, April 06, 2006 12:57 AM To: Tomcat Developers List Subject: Re: configurable AJP Buffer Size Henri Gomez wrote: well client and server should be in phase about the buffer size and the better way to accomplish that will be via AJP13 extensions (ie AJP14), with connect time negociation datas like packet buffer size :) Right. Extensions could contain packet size. The problem is that even with the custom size that size would be limited to 32K, and again someone will complain about that limitation ;) Possible. But, I have no idea why connector should be constraining this. - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
Henri Gomez wrote: Just take a look at the AJP protocol documentation : http://tomcat.apache.org/connectors-doc/common/ajpv13a.html Packets sent from the server to the container begin with 0x1234. Packets sent from the container to the server begin with AB (that's the ASCII code for A followed by the ASCII code for B). After those first two bytes, there is an integer (encoded as above) with the length of the payload. Although this might suggest that the maximum payload could be as large as 2^16, in fact, the code sets the maximum to be 8K. So to support more than 64k bytes, we should have a whole new code on Apache and Tomcat side and break compatibility with all current implementations. And that's bad ;( We recently saw a customer run into this limitation in that all of their headers, etc, would not fit in the first 8K. Waiting for a new AJP version sounds like a non-starter. Can we just have something like a JkOption that allows one to explicitly opt into this arrangement? Address this for mod_jk and Tomcat and one is done for now (though a mod_proxy_ajp shouldn't be far behind). Take a look at the AJP13 extension proposal : http://tomcat.apache.org/connectors-doc/common/ajpv13ext.html We could plug many usefull informations in LOGIN INIT for example ! These proposals all look interesting. The problem is that there are lots of proposals and this would seem to inevitably take quite some time to stabilize all of this in mod_jk, mod_proxy_ajp, and Tomcat (native and Java). I'd love to be proven wrong, though. -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
2006/4/6, Jess Holle [EMAIL PROTECTED]: Henri Gomez wrote: Just take a look at the AJP protocol documentation : http://tomcat.apache.org/connectors-doc/common/ajpv13a.html Packets sent from the server to the container begin with 0x1234. Packets sent from the container to the server begin with AB (that's the ASCII code for A followed by the ASCII code for B). After those first two bytes, there is an integer (encoded as above) with the length of the payload. Although this might suggest that the maximum payload could be as large as 2^16, in fact, the code sets the maximum to be 8K. So to support more than 64k bytes, we should have a whole new code on Apache and Tomcat side and break compatibility with all current implementations. And that's bad ;( We recently saw a customer run into this limitation in that all of their headers, etc, would not fit in the first 8K. Waiting for a new AJP version sounds like a non-starter. Can we just have something like a JkOption that allows one to explicitly opt into this arrangement? Address this for mod_jk and Tomcat and one is done for now (though a mod_proxy_ajp shouldn't be far behind). Well it could be done like this. Take a look at the AJP13 extension proposal : http://tomcat.apache.org/connectors-doc/common/ajpv13ext.html We could plug many usefull informations in LOGIN INIT for example ! These proposals all look interesting. The problem is that there are lots of proposals and this would seem to inevitably take quite some time to stabilize all of this in mod_jk, mod_proxy_ajp, and Tomcat (native and Java). I'd love to be proven wrong, though. Not necessary, if you take a look at curent jk/ajp implementations (native and java), there is allready code in it for AJP14 support :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
Henri Gomez wrote: These proposals all look interesting. The problem is that there are lots of proposals and this would seem to inevitably take quite some time to stabilize all of this in mod_jk, mod_proxy_ajp, and Tomcat (native and Java). I'd love to be proven wrong, though. Not necessary, if you take a look at curent jk/ajp implementations (native and java), there is allready code in it for AJP14 support :) Including the ability to increase the packet size (or specifically to use a larger packet if necessary to capture all the headers)? How stable is AJP13 functionality in this code? I currently only need this one additional feature :-) -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
KARNATI, SRINIVASA R [AG/1000] wrote: Possible. But, I have no idea why connector should be constraining this. ??? It is obvious by your comment that you have no clue how AJP protocol works, and why it has a fixed packet size in the spec. Also take a look at what protocol and specification means. According to your proposal one could say: When using http I wish that header name for content-length is now 'CL'; I please all the vendors to support my idea. -- Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
2006/4/6, Mladen Turk [EMAIL PROTECTED]: Jess Holle wrote: Henri Gomez wrote: We recently saw a customer run into this limitation in that all of their headers, etc, would not fit in the first 8K. Waiting for a new AJP version sounds like a non-starter. Can we just have something like a JkOption that allows one to explicitly opt into this arrangement? Address this for mod_jk and Tomcat and one is done for now (though a mod_proxy_ajp shouldn't be far behind). -1. Guys we are talking about protocol! Saying that one part can send a 32K while the other part is expecting 8K will in most cases lead to core dump. If the size is larger then 8K, this is not an AJP13 protocol any more, and I'll be -1 on any attempt to extend the packet size. Like said, we can talk about AJP14, but AJP13 is well established protocol, and ideas that tries to break it will never pass. Well configuring as I said previousy, settings buffer sire in mod_jk (via jkOptions or others way) couldn't be done without doing/settings the same on the Tomcat side. And that code is not present today in jk of course, but need to be introduce in all the Tomcat base (3.3/4.0/4.1/5.0 and 5.5). May be the better will be to discuss what should be the foundation of AJP13 successor. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: configurable AJP Buffer Size
-Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 12:21 PM To: Tomcat Developers List Subject: Re: configurable AJP Buffer Size KARNATI, SRINIVASA R [AG/1000] wrote: I would like to extend AJP buffer size (in org.apache.jk.common.MsgAjp) as a configurable option. We really needed the buffer above 8 kb (because of Kerberos integration.) -1. Makes no sense because other side has no clue about that. I will be implementing the similar configurable option for the client-end of the connector also (for ex., for isapi_redirector, via registry setting) This gives us at least the needed flexibility of specifying the size, and also will be able to keep up with the later releases. If you need larger packet size make your own flavor of Tomcat and mod_jk or mod_proxy_ajp or isapi_redirector with desired maximum packet size. This will be too constraining. It will not be AJP1/3 compliant for sure. I hope there is something I can do that becomes part of the existing protocol. I am willing to spend time on that. Thanks, Srini - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
well client and server should be in phase about the buffer size and the better way to accomplish that will be via AJP13 extensions (ie AJP14), with connect time negociation datas like packet buffer size :) 2006/4/5, KARNATI, SRINIVASA R [AG/1000] [EMAIL PROTECTED]: -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 12:21 PM To: Tomcat Developers List Subject: Re: configurable AJP Buffer Size KARNATI, SRINIVASA R [AG/1000] wrote: I would like to extend AJP buffer size (in org.apache.jk.common.MsgAjp) as a configurable option. We really needed the buffer above 8 kb (because of Kerberos integration.) -1. Makes no sense because other side has no clue about that. I will be implementing the similar configurable option for the client-end of the connector also (for ex., for isapi_redirector, via registry setting) This gives us at least the needed flexibility of specifying the size, and also will be able to keep up with the later releases. If you need larger packet size make your own flavor of Tomcat and mod_jk or mod_proxy_ajp or isapi_redirector with desired maximum packet size. This will be too constraining. It will not be AJP1/3 compliant for sure. I hope there is something I can do that becomes part of the existing protocol. I am willing to spend time on that. Thanks, Srini - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configurable AJP Buffer Size
Henri Gomez wrote: well client and server should be in phase about the buffer size and the better way to accomplish that will be via AJP13 extensions (ie AJP14), with connect time negociation datas like packet buffer size :) Right. Extensions could contain packet size. The problem is that even with the custom size that size would be limited to 32K, and again someone will complain about that limitation ;) AJP14 should have by default both connect and disconnect packets in a CPING/CPONG fashion. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
