DevHeads.net

Reply to comment

Re: "proxy_balancer" | stickysession

By Rainer Jung at 10/15/2010 - 09:26

On 15.10.2010 12:32, King Holger (CI/AFP2) wrote:
Good to know.

So we deduce, that either the request is still hanging inside Tomcat or
it never reached Tomcat. Although the latter is more likely, you can
check: if you have the Tomcat manager webapp deployed, you can look at
the status page, which shows a list of all in-flight requests.

Then there's likely no way forward for this incident. We would nee dto
wait for the next one :(

Good, it's helpful in a lot of situations anyhows.

Sorry, to many possible reasons in the proxy for that. You need the
error log.

You can try to make your setup a bit more robust by looking at the
parameter table given at

<a href="http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypass" title="http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypass">http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypass</a>

For the ajp workers, the following parameters come to mind:

- ping (e.g. ping=10s)
- connectiontimeout (e.g. connectiontimeout=10s)
- timeout (e.g. timeout=120s)
- keepalive=On

The 10 second timeouts could also be lowered to e.g. 5 or 2 seconds if
you are reasonably sure that you don't have any longer GC pauses on the
Java back-ends. A good value for the general timeout depends on your
expectation of response times the back-end will be able to support as
long as it is running well. The "%D" in the access log will help you get
some real numbers.

Regards,

Rainer

Reply