Logs show reasonable request handling duration, but proxied clients timing out

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA8E25.9917A0F2
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

For sometime I've had complaints from one of the users of a particular
mod_perl handler that is timing out on their end. They are using a
programmatic Java client, accessing a mod_perl registry handler that
simply returns a text file.

=20

The client is accessing my servers via a proxy which then connects to a
load balancer that balances between two of my boxes.

=20

The client uses a 500 millisecond read timeout which is often reached,
causing the client process to throw exceptions. However, when I look at
my logs, the %D param shows durations well below this limit.

=20

At times I do not see the requests at all.

=20

What should I be looking at on my servers to see if the problem is on my
end?

=20

As much as it appears that the problem is in the proxies, I want to make
sure that I've covered all the bases from my end before I escalate the
issue.

=20

There are no fixup handlers or log handlers, which I believe might
impact post-logging timings.

=20

Thanks, everybody.

=20

Eric


_______________________________________________

This e-mail may contain information that is confidential, privileged or o=
therwise protected from disclosure. If you are not an intended recipient =
of this e-mail, do not duplicate or redistribute it by any means. Please =
delete it and any attachments and notify the sender that you have receive=
d it in error. Unless specifically indicated, this e-mail is not an offer=
=20to buy or sell or a solicitation to buy or sell any securities, invest=
ment products or other financial product or service, an official confirma=
tion of any transaction, or an official statement of Barclays. Any views =
or opinions presented are solely those of the author and do not necessari=
ly represent those of Barclays. This e-mail is subject to terms available=
=20at the following link: www.barcap.com/emaildisclaimer. By messaging wi=
th Barclays you consent to the foregoing. Barclays Capital is the invest=
ment banking division of Barclays Bank PLC, a company registered in Engla=
nd (number 1026167) with its registered office at 1 Churchill Place, Lond=
on, E14 5HP. This email may relate to or be sent from other members of t=
he Barclays Group.
_______________________________________________

------_=_NextPart_001_01CA8E25.9917A0F2
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

schemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html=
40">


>

style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"> style=3D"FONT-SIZE: 11pt"> face=3D"Times New Roman">_______________________________________________<=
?xml:namespace=20
prefix =3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/>

style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"> style=3D"FONT-SIZE: 11pt"> face=3D"Times New Roman"> 

style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"> style=3D"FONT-SIZE: 11pt">This e-mail may =
contain=20
information that is confidential, privileged or otherwise protected from =

disclosure. If you are not an intended recipient of this e-mail, do not=20
duplicate or redistribute it by any means. Please delete it and any attac=
hments=20
and notify the sender that you have received it in error. Unless specific=
ally=20
indicated, this e-mail is not an offer to buy or sell or a solicitation t=
o buy=20
or sell any securities, investment products or other financial product or=
=20
service, an official confirmation of any transaction, or an official stat=
ement=20
of Barclays. Any views or opinions presented are solely those of the auth=
or and=20
do not necessarily represent those of Barclays. This e-mail is subject to=
=20terms=20
available at the following link: style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial; mso-ansi-langu=
age: EN-GB; mso-fareast-language: EN-GB"> href=3D"http://www.barcap.com/emaildisclaimer">www.barcap.co m/emaildiscla=
imer.=20
By =
messaging=20
with Barclays you consent to the foregoing. style=3D"mso-spacerun: yes">  Barclays Capital is the investm=
ent=20
banking division of Barclays Bank PLC, a company registered in space=20
prefix =3D st1 ns =3D "urn:schemas-microsoft-com:office:smarttags" /> :place=20
w:st=3D"on">England<=
/st1:place>=20
(number 1026167) with its registered office at w:st=3D"on">1 Churchill Place, City=20
w:st=3D"on">London, E14=20
5HP.&nbs=
p;=20
This email may relate to or be sent from other members of the Barc=
lays=20
Group. AN>

style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"> style=3D"FONT-SIZE: 11pt"> face=3D"Times New Roman">_______________________________________________<=
/FONT>

Re: Logs show reasonable request handling duration, but proxied

On Tue, Jan 5, 2010 at 11:39 AM, wrote:
> The client uses a 500 millisecond read timeout which is often reached,
> causing the client process to throw exceptions.=A0 However, when I look a=
t my
> logs, the %D param shows durations well below this limit.
>
> At times I do not see the requests at all.

Sounds like a network problem.

> What should I be looking at on my servers to see if the problem is on my
> end?

You could try turning off keep-alive, in case the proxy handles that
poorly. You could also set up a monitor script to hit the URL every 5
minutes and log the times. Maybe try doing that directly and through
the proxy to compare.

- Perrin