Apache 1.3: extended times in access_log

Hello!

Briefly :
How can configure logging in apache additional time access client to
the server :
- the first byte request from the client,
- the last byte request from client
- first byte reply

Problem description :
I have the problem of slow response time from HTTP-client to HTTP-
server (Apache 1.3 + Java). The analysis shows that the server code is
very fast, always two seconds faster. Setting time_taken in access_mod
(parameter %T) shows that the Apache always logging HTTP transaction
time is two seconds or less.
Same time, client have timeout one or more minute by waiting response
from server.
Problem occurs in 3 days stable.
I would like to get an accurate picture of the slowdown, a bottleneck
and try to solve the problem.

Thank you

On Jun 22, 11:50 am, Sergius <Serge.Is....TakeThisOut@gmail.com> wrote:
> Hello!
>
> Briefly :
> How can configure logging in apache additional time access client to
> the server :
> - the first byte request from the client,
> - the last byte request from client
> - first byte reply
>
> Problem description :
> I have the problem of slow response time from HTTP-client to HTTP-
> server (Apache 1.3 + Java). The analysis shows that the server code is
> very fast, always two seconds faster. Setting time_taken in access_mod
> (parameter %T) shows that the Apache always logging HTTP transaction
> time is two seconds or less.
> Same time, client have timeout one or more minute by waiting response
> from server.
> Problem occurs in 3 days stable.
> I would like to get an accurate picture of the slowdown, a bottleneck
> and try to solve the problem.
>
> Thank you

use wireshark to see when the requests and responses occur, and if
there are network troubles.
Use a few proxies (phproxy/w3c validator...) to check its not just one
client - it may be their network, do they have the same trouble after
they have made one successful connection - then is it faster for
subsequent requests.
THen can you check the server using a LAN computer, this will rule out
firewall troubles at the border...
post back results