(IIRC) Successful (and unsucessful?) DNS lookups are cached forever during the life of the JVM. So if you start tomcat on Jan 1, 2003 and tomcat looks up foo.com that day - the lookup (across the network) is not done again. So if the address changes Jan 2 tomcat will have the wrong answer. And continue to have the wrong answer until the JVM is restarted.
Yes - this stinks for long running servers. I do not know if this is still an issue in JDK 1.4.
Once way to get around this is to find a class which re-implements the DNS protocols. (ICK)
-Tim
Ron Day wrote:
Do you know which class cache the negative response............
-----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:07 AM To: Tomcat Users List Subject: RE: crontab problems
Because the underlying classes sometimes cache a negative
response, so you have to restart tomcat to enable a new lookup. (That's not specific to tomcat)
-----Original Message----- From: Hannes Schmidt [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 3:02 AM To: Tomcat Users List Subject: Re: crontab problems
Regarding your problem: I don't understand why bouncing Tomcat would resolve a DNS problem. The UnknownHostException is a indication that something is wrong with DNS or the
resolver library.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
