Do you have a firewall installed? If yes check timeouts on idle connections there. Do you have keepalive enabled? What is the timeout there? Sometimes reducing it might help.
On Wed, May 21, 2008 at 1:10 PM, Dragon <[EMAIL PROTECTED]> wrote: > Danie Qian wrote: > >> do a quick test to see if you get any packet loss: >> ping -t <http://www.your-server-name.com>www.your-server-name.com >> > ---------------- End original message. --------------------- > > Considering that many servers these days are configured to not respond to > ICMP echo requests, that may well be pointless. > > It may be possible to get a bit more useful information using tracert, that > will hopefully give an idea where any excessive latency is occurring. Then > again, it may not. > > A single invocation of tracert may not give any real useful data either as > it only looks at the current conditions and reports the response latency > between hops as they are when the test is run. Network traffic can change > these things dramatically over time. It is possible that one time you get a > clean, fast run and another you get indications of a slow down. > > Now it sounds to me that the OP is seeing a problem with the TCP/IP > sessions between the client and server being closed prematurely. Why that is > occurring is unclear. It is probably going to take some low-level analysis > of the packets to determine what is going on. > > > > Dragon > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
