Just a quick followup on this message. I think Nick's theory on DNS was
right. I talked to my ISP provider, and they do a DNS lookup in the switch
for every web request. So, even though the server and client weren't doing
DNS lookups, the intermediate network was. And the symptoms of the probl
Hi Nick,
I'm puzzled by the client DNS theory, since I had the host (in Windows, mind
you) directly mapped in /etc/hosts. (the Windows equivalent).
The argument in favor of the DNS theory is that we ran a web test of DNS
with www.dnsreports.com and it reported several problems. (we were using
On Fri, 31 Aug 2007 06:46:37 -0700 (PDT)
wglass <[EMAIL PROTECTED]> wrote:
>
> Thanks, Nick.
>
> Can you explain your question about DNS?
If it's one vhost, that suggests the possibility of an issue
with DNS lookups at the client end.
> What's the easiest way to get and test an HTTP/1.0 client
Thanks, Nick.
Can you explain your question about DNS? My assumption is that if I had a
reverse DNS issue, I could identify it by running tcpdump on port 53 on the
server. (e.g. with HostnameLookup) I did this and saw no TCP/UDP traffic.
To eliminate the possibility of client DNS issues, I har
On Fri, 31 Aug 2007 02:23:38 -0700 (PDT)
wglass <[EMAIL PROTECTED]> wrote:
> * I suspected DNS/reverse DNS issues. But I ran a tcpdump on port 53
> and saw no signs of DNS queries
It does look an obvious candidate. And why would DNS be generating
traffic (let alone TCP traffic) on the server?
Hi,
I've had a bizarre performance problem earlier this week and I can't figure
it out. It'd be great if anyone had suggestions.
Twice recently, I've had extremely slow performance serving static files
from a single virtual host on my Apache server. Files that were sent to
Tomcat with mod_jk r
