For jdk1.4 you should be able to set the networkaddress.cache.negative.ttl system property to control this. (Assuming the lookups are made using the java.net.* sub-system)
http://java.sun.com/j2se/1.4/docs/guide/net/properties.html
http://java.sun.com/j2se/1.4.1/networking-relnotes.html


We're still on 1.3.x in production :(

Oscar Carrillo wrote:

How bizarre. AFAIK, this is the same problem MS Windows has with
it's DNS implementation. That's why IE never can re-connect after it
gets a bad DNS lookup.

Oscar

On Wed, 26 Feb 2003, Ralph Einfeldt wrote:



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]



Reply via email to