-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Razi,
On 4/22/15 6:39 PM, Razi Ansari wrote: > -------- Original message -------- From: Christopher Schultz > <ch...@christopherschultz.net> Date: 04/23/2015 6:15 AM > (GMT+08:00) To: Tomcat Users List <users@tomcat.apache.org> > Subject: Re: Apache Tomcat jk connector 400 bad request > >> If you decide to change your timeout values (I don't see a reason >> to >> >> do so unless you are encountering some kind of related problem, >> and I >> >> don't consider this to be a related problem), make sure they are >> >> consistent between mod_jk and Tomcat's AJP connector. > > I tried inceasing the value of webserver KeepAliveTimeout to 15 and > i dont get the 400 bad request error in the test environment. But > i really want to know the root cause before i move it to > production. In my httpwatch i see the request going without any > body ony header. Without the change in KeepAliveTimeout, can you reproduce this error in your test environment? I would honestly be surprised if KeepAliveTimeout is the trouble, here. For the AJP connector, the KeepAliveTimeout is not relevant because AJP is by definition keep-alive. You can disable it if you think doing so will improve the situation, but I don't have any reason to suspect it would. It would be great to know whether the AJP connector or the HTTP connector was the one failing. In Tomcat, the stack trace will include the thread identifier which includes the port number and protocol being used. Please include that with your stack traces when you find the m. It would also be great to know which (exact) version of Tomcat is being used under the hood. Check the logs during startup to see what Tomcat says it is. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVODbWAAoJEBzwKT+lPKRYiBkP+QENinLAv9vXdjDi598Av56n nin9n4jzkgVaMC7h/EpzM81w7rjVoNdfD9d3j472hQFyUY+x9iQwDxNRc25t7VHH jwq21AZBqRDn6hNvLxxpXyKqVuLImZ08GFzI4PdelIQ0IuZ2WlRQwW1xNtcVZKgh yq1/Az1zK82rzrIH8WJhu0frYNd5mqrrEEVCQfUs3pEJyqf0uQFM8buVVKScla3x sb6qjo3+XCHGZ/KXFllr0t0E7fGlk7xP8NhRLzSO7AkDvUgk7SzAryN2VmwbTn3w KbO3bzT7dQse+1ykj246L+TqIWJOsycooGagTRtH7kW/5jRXS6b8kLL08XhLY70z Ybcfbd1gwIbihm29LsOaU54hWTyQYa5cSAzCXEaQsGUfaoDsuU4L69Uf+G40QcO6 c1cCvJImSFjpmVcoVtVitT+U6vDDK0kIcuyrb766GCyde2pRlFswCMho2GN2yT6L 2e9v9xqmLANZE0iaJpK2qUVE/efh1m+API/wFYXqnQhe2S5V8fXAGXM/rJdeOQNL IXMZN4E1moVClbaKVn+TbtcexR9nmU6GPyaL+VoJauDJf5UV5Y31+wp+XgP1k13/ wQ0LoumpioPYp7QEbrSgNTUF5I2Q+Cp7VGtoO3PPDWzgcBH8eSiqHVnsC2da51k8 sjaBXvJn5/taUN49pEGo =0W9M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
