Re: mod_proxy_ajp: (120010)APR does not understand this error code: proxy: AJP: request failed to (null) (*)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Could this help you?
http://www.jboss.org/community/docs/DOC-12529

Ivars


   Going over the 8K AJP headers limits:

The default size of a AJP package is 8K as the http headers are sent only in the first packet it could be needed to overcome the limit.



To reach this you need to add packetSize parameter in the <Connector/> parameter like:



|
   <Connector port="8009" protocol="AJP/1.3"
              packetSize="20000"
              redirectPort="8443" ></Connector>
|

and ProxyIOBufferSize (also LimitRequestFieldsize probably) directive in httpd.conf too. For example:



|
ProxyIOBufferSize 19000
LimitRequestFieldsize 18000
|

packetSize is supported since Tomcat 5.5.21 and Tomcat 6.0.1.



Torsten Krah wrote:
Hi,

i am facing some problems connecting tomcat ajp with apache through mod_proxy_ajp:

The log shows often something like this:

#############################################################################
ajp_marshal_into_msgb - No such method ssiers%2FM%25C3%25BCllskandal%22%3B%7D
ajp_send_header: ajp_marshal_into_msgb failed
(120010)APR does not understand this error code: proxy: AJP: request failed to (null) (*)
request failed: error reading the headers
ajp_marshal_into_msgb: Error appending the header value
ajp_send_header: ajp_marshal_into_msgb failed
(120001)APR does not understand this error code: proxy: AJP: request failed to (null) (*)
#############################################################################


According to the error.log messages code 400 bad request are shown in access.log - looking at the timestamps i guess they are connected to each other.
Reading through the lists i did found following archive message:

http://www.mail-archive.com/users@xxxxxxxxxxxxxxxxx/msg57693.html

The answer is that the request headers have to fit into 8Kb or the request fails.
Looking at the failing request the cookie information is more than 8Kb.
Looking at the AJP3 docs here:

http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html

reading at the end this scenario is mentioned and causes a failing connector.

Looking at the apache docs:

http://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html

there is only mentioned that the packet size is 8Kb (much of the code ...).

The failure case question is missing here.
So my question is - have i have to force the application to minimize the cookie size to get the request header into the first 8Kb packet or is there another way how to handle this?

http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestfieldsize

With this directive the maximum header size can be increased - does this work for mod_proxy_ajp too?

thx for help

Torsten


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux