darinpope schrieb:
It's an (un)documented attribute called "packetSize" for the AJP connector:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44541
The packetSize attribute is only good for 5.5.20+ and 6.0.2+.
However, I'm having issues with this myself. I've set my max_packet_size in
the worker and the packetSize in the AJP connector to the same values, but
when I look at the mod_jk.log, it appears that it is still using 8192:
received from ajp13 pos=0 len=8188 max=32768
If anyone has an answer to this issue, I'd appreciate an answer.
Darin
obalas wrote:
Hello, everybody,
Can anyone help me out with this problem, i need to increase the header
size for the AJP connector to at least 16K, and I noticed from the
documentation that, unlike the standard connector on port 8080, the AJP
connector does not recognize the maxHttpHeaderSize attribute.
Does anybody know a workaround solution for this?
Thanks in advance,
Ovi
The posted message comes from an AJP packet send by Tomcat back to
mod_jk. The original motivation for increasing the AJP packet size was
handling long HTTP headers (like when the client uses an SSL
certificate, this was mostly broken with the default (KB size). It seems
that Tomcat doesn't use the bigger size in its response packets, which I
think is fine, because we don't expect a huge performance benefit from
bigger packets/buffers (maybe even a negative result).
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
