Great, thank you, I'll give it a try. It's also documented at: http://java.sun.com/j2se/1.4/docs/guide/net/properties.html
Thanks, Adi > On Sun, 8 Dec 2002 13:08:16 -0800, "Schnitzer, Jeff" <[EMAIL PROTECTED]> said: > I had to deal with this last week. Here's the important bit of > documentation: > http://java.sun.com/j2se/1.4.1/docs/api/java/net/InetAddress.html > Jeff Schnitzer [EMAIL PROTECTED] The Sims Online > -----Original Message----- > From: Aditya [mailto:[EMAIL PROTECTED]] > Sent: Saturday, December 07, 2002 6:28 PM > To: [EMAIL PROTECTED] > Subject: JVM or tomcat aggressive caching DNS lookups? > > This seems to be a problem with the JVM, but since I only run into it > in long running programs like Tomcat, I'm asking here -- it seems > that in an JSP, if I'm using URLConnection to retrieve a remote > webpage, the IP address that is obtained when doing the lookup in > URLConnection persists for the life of Tomcat/JVM even past the ttl > for that record. For example: > > - www.foo.com resolves to 1.2.3.4 with a ttl of 15 minutes > > - 30 minutes later, if I look up www.foo.com, it's still 1.2.3.4 > though in the meantime I've updated it to 4.5.6.7 > > Is there a way to force the JVM internal DNS cache to be flushed? > > Thanks, Adi > > -- To unsubscribe, e-mail: <mailto:tomcat-user- > [EMAIL PROTECTED]> For additional commands, e-mail: > <mailto:tomcat-user- [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
