I checked the properties file and I am using defaults, so cache on unsuccessful should be 10 secs. Mine is sure acting like it is "Forever" (until new jvm is started)
ron -----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 6:36 AM To: Tomcat Users List Subject: RE: crontab problems It's the java implementation that does the caching, as java implements the lookup on it's own and doesn't use the operating system functions for that. (That doesn't mean that the operating system or the resolver lib is not caching, but that is independent of the java problem.) The lookup behaviour can be configured, have a look at: http://java.sun.com/j2se/1.4/docs/guide/net/properties.html#nct http://java.sun.com/j2se/1.4/docs/guide/net/properties.html#ncnt > -----Original Message----- > From: Hannes Schmidt [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 26, 2003 1:01 PM > To: Tomcat Users List > Subject: Re: crontab problems > > Where do you get your excepetion? My guts is telling me that > the lookup result is cached by the operating system rather > than a Java class. On the other hand, caching a negative result > should never be done by anything. --------------------------------------------------------------------- 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]
