Bug 58249 - Documentation regarding max_packet_size parameter not correct
Summary: Documentation regarding max_packet_size parameter not correct
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 1.2.40
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2015-08-17 10:22 UTC by Gunnar Adams
Modified: 2016-09-19 13:58 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Adams 2015-08-17 10:22:49 UTC
isapi and mod_jk(?)

max_packet_size is documented to be the maximum number in Bytes used by the AJP protocol. There is no mention that the actually used buffer size is actually aligned to the next 1024 Byte. In Tomcat, the packetSize parameter is used as is, e.g. if you specify a buffer of 32000 bytes, Tomcat will use and expect a maximum size of 30000 bytes, while (at least the ISAP redirector for IIS) will send 30720 bytes. Either alignment in the connector should be changed or documentation should indicate, that only 1024byte-aligned values should be supplied.

The problem has been found during debugging of isapi connector for IIS.
Comment 1 Mark Thomas 2016-09-19 13:58:47 UTC
Thanks for the report. This has been fixed in trunk and will be included in 1.2.42 onwards.