-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordan,
On 12/3/2010 2:56 PM, Jordan Michaels wrote: > It's what makes me think that the... > > sun.net.client.defaultConnectTimeout (default: -1) > sun.net.client.defaultReadTimeout (default: -1) > > settings are involved somehow... - From the docs (http://download.oracle.com/javase/1.5.0/docs/guide/net/properties.html): " These properties specify the default connect and read timeout (resp.) for the protocol handler used by java.net.URLConnection. " This has absolutely nothing at all to do with DNS resolution. Is the problem that a hostname (somehow) resolves to NXDOMAIN and /that/ value is being cached? I'm pretty sure that the JVM delegates to the OS to do DNS resolution, so the caching would only be a problem if a DNS record /changed/ during the lifetime of the JVM. IIRC, DNS shouldn't cache NXDOMAIN in general. You could easily try setting the ttl configs mentioned in other posts to be 0 (zero: do not cache) and see what happens. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz5U2MACgkQ9CaO5/Lv0PBUvgCgg4dl9V9ybFW2c+KB4v3yoDAX SvkAn3wqxUJbwj3r+PYi4Zrwrb3WJiD5 =S+sQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
