In my case I am deploying the application via Java Web Start, so I am
not guaranteed access to the java.security file on end user machines. I
have to do it either via the -D command line option or programmatically
via System.setProperty(). Currently I am doing it programatically.
Aaron
Kenneth Wilcox wrote:
I think those properties need to be set in the security file, not as -D
parameters - agree?
Ken
-----Original Message-----
From: Aaron Braeckel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 22, 2005 4:19 PM
To: [email protected]
Subject: DNS Cache Timeout
Hello,
I am using HttpClient 3.0RC2 with an application that runs constantly
and contacts a web server frequently. I am switching DNS entries to
point to the backup server if problems occur with the primary server.
Currently I am not seeing any recognition of the change when I switch
the DNS entry, so it seems like a client-side DNS caching issue. Is
there any way to specify DNS cache timeouts (or even whether or not to
use caching) with HttpClient? I wasn't able to find any information on
this topic anywhere.
I am setting the appropriate properties to restrict DNS caching through
Java core methods (setting "sun.net.inetaddr.ttli" and
"networkaddress.cache.ttl¨) but so far I have not seen any effect.
Thanks,
Aaron
---------------------------------------------------------------------
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]
