-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
I'm slowly switching from mod_jk to mod_proxy_ajp and I have a
development environment where I'm getting Bad Gateway responses sent
to clients along with this exception in my Tomcat log file:
java.lang.IllegalArgumentException: Header message of length [8,194]
received but the packetSize is only [8,192]
at
org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:685)
at
org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:626)
at
org.apache.coyote.ajp.AjpProcessor.refillReadBuffer(AjpProcessor.java:73
4)
at
org.apache.coyote.ajp.AjpProcessor$SocketInputBuffer.doRead(AjpProcessor
.java:1456)
at org.apache.coyote.Request.doRead(Request.java:581)
at
org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java
:344)
at
org.apache.catalina.connector.InputBuffer.checkByteBufferEof(InputBuffer
.java:663)
at
org.apache.catalina.connector.InputBuffer.readByte(InputBuffer.java:358)
at
org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.j
ava:93)
at
org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:
53)
at
org.apache.commons.io.input.TeeInputStream.read(TeeInputStream.java:106)
at java.io.FilterInputStream.read(FilterInputStream.java:83)
at my.product.MacInputStream.read(MacInputStream.java:29)
at java.io.FilterInputStream.read(FilterInputStream.java:83)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInput
Stream.read(XMLEntityManager.java:2890)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEnt
ity(XMLEntityManager.java:674)
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocV
ersion(XMLVersionDetector.java:148)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:806)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:771)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
a:141)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Abstr
actSAXParser.java:1213)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.pars
e(SAXParserImpl.java:643)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImp
l.java:327)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
This is a web service which is reading the request with a SAXParser.
It's been running in production (and dev!) for years without any
issues. It''s been running for a few months in development, now, with
mod_proxy_ajp without any errors.
I know about the "max packet size" and the default is 8192 bytes. I
haven't changed the default. Here's my <Connector> configuration:
<Connector port="8245"
address="127.0.0.1"
secretRequired="false"
redirectPort="443"
protocol="AJP/1.3"
URIEncoding="UTF-8"
executor="tomcatThreadPool" />
Here's the configuration in httpd.conf:
<Proxy "balancer://my-api">
BalancerMember "ajp://localhost:8245" timeout=300
ping=5 ttl=60
</Proxy>
ProxyPass "/my-api/" "balancer://my-api/my-api/"
ProxyPassReverse "/my-api/" "balancer://my-api/my-api/"
The documentation for mod_proxy_ajp[1] seems to indicate that the
"Packet Size" for AJP is fixed at 8192 bytes:
"
Packet Size
According to much of the code, the max packet size is 8 * 1024 bytes
(8K). The actual length of the packet is encoded in the header.
Packet Headers
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*.
"
(emphasis mine)
Does anyone know under what circumstances mod_proxy_ajp might send
more than 8192 bytes? It looks like mod_proxy_ajp doesn't have any way
to set the max packet size like mod_jk does.
I should probably be able to set the max packet size on the Tomcat
side to something higher than 8192 to catch this kind of thing... but
it looks like it might be a bug in mod_proxy_ajp.
Versions are Apache httpd 2.4.25 (Debian) and Tomcat 8.5.trunk
(8.5.55). mod_jk is not being used.
Any ideas?
- -chris
[1] https://httpd.apache.org/docs/2.4/mod/mod_proxy_ajp.html
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7zY1MACgkQHPApP6U8
pFjB9xAAn6Qx/3oxL9LrE716x84vACmUiiFeSY/8VeDYdNuys9+s2ULrARdx62rC
61hV1y1pNwVVK4ZlwxF/DVVUhClfqb3P/lbR76gOWwNJvJs4qXpqF7PSVHyMD3LR
3ze8XXK8NMZMEPoMrOwg3wI7mQoQpj66QhD3fMNz4hbp2iwxXzZfVDLN7D/g8/6Y
E4vseY44x1mLQ5BlBy7DGEwpdrVQR50tW8BG4uPfWgyZlnkf5o4AHX7s0oAgLzep
VCFCXMK3tYArQrZNv+k7yOgb7Lk4dacRt8pd5Wf2VVHy+1sBZwpRcFXaD0O6N2lc
T27F88H0HMsz7J1K6Q52zn0O7nzfk3PbkaXY95SC6zM4jNMRMt35UTYg9UTN8eH9
1RcfXROvZbbH/w/+oDXDZEtNhytzdZIYTbKpSHuyoLW/GJD2A31okinncFlFmcYH
0Bsjh7UGptHqaDpIhIOcVysweW+hNK9AoeaswFfzJR29ofRoNkpX+BuB8DO+4Q06
UHVYehvnreUuyKwKXwWhMf9TWAVZH/3b01X/EywVq30w27i5LbSKsH5Mh5POzbFW
koHousK9Fsh2hYSKgifkB/6e+TruOCwgB0cjDQR2uG59r6DaBwrTjfsEdIbHKGNb
oyV/4KO/Bc4lQhbRYKUo0j2v1IKm+/yRpzvGucDcWWSv4u/hw2g=
=ARLB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
