failed appending the query string of length 7295 in Apache Tomcat

We're getting the following error when the HTTP GET request is large:
mod_jk.log:[Wed Oct 18 11:37:20.232263 2017][12082:139812138850048] ajp_marshal_into_msgb::jk_ajp_common.c (517): failed appending the query string of length 7295

I've found several references to this error and I've tried the following, but it did not work:
1. Added worker.template.max_packet_size=65536 to this file: workers.properties
2. Added packetSize to file /usr/apache-tomcat/conf/server.xml:
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" address="127.0.0.1" protocol="org.apache.coyote.ajp.AjpNioProtocol"
                        socket.directBuffer="true"
                        URIEncoding="UTF-8" redirectPort="8443" packetSize="65536" connectionTimeout="120000"  />
3. Added LimitRequestLine 65536 LimitRequestBody 0 LimitRequestFieldSize 65536 LimitRequestFields 10000 (to /nbsnas/http/conf/httpd.conf file)
Restarted Apache for each of the above and also when all of them are set to the values above.

I'm still getting the same error.
Any ideas/recommendations is greatly appreciated.
thanks!
Vamsi DAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dr. KlahnPrincipal Software EngineerCommented:
You might try setting

JkLogLevel trace

Open in new window


in the config file.  This should let you know exactly where in mod_jk the problem is occurring, and you can then read the source to see what's going on or add more detailed debugging info to the mod_jk source.

Of course, this is going to generate enormous logs very rapidly in production -- so you want to try it only on a testbed system and feed it only the offending request.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dr. KlahnPrincipal Software EngineerCommented:
No further input from requester.  Troubleshooting approach that would reveal the source of the problem was provided.  Points assigned to sole responder.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.