Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
From: "Kenneth Wilcox" <kwilcox75@cox.net>
To: "'HttpClient User Discussion'" <httpclient-user@jakarta.apache.org>
Subject: RE: DNS Cache Timeout
Date: Sun, 26 Jun 2005 22:24:39 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <42BAE9E2.3070407@ucar.edu>
Thread-Index: AcV4FJqyR+m93rtAQ66+tHGbrgA7NACqkiog
Message-Id: <20050627022440.SVIL13442.lakermmtao05.cox.net@zeus>

I guess what I am saying is that I believe System.setProperty will not =
work.
You need to set the property with the Security class because you are =
setting
a property that is specified in the security file

java.security.Security.setProperty("networkaddress.cache.ttl" , =
"10000");

And yes, Java by default caches DNS entries forever unless you override =
it
with the setting above.

Let me know if that helped, I believe this will solve your issue.

-Ken


> -----Original Message-----
> From: Aaron Braeckel [mailto:braeckel@ucar.edu]
> Sent: Thursday, June 23, 2005 12:57 PM
> To: HttpClient User Discussion
> Subject: Re: DNS Cache Timeout
>=20
> 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.
>=20
> Aaron
>=20
> 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:braeckel@ucar.edu]
> >>Sent: Wednesday, June 22, 2005 4:19 PM
> >>To: httpclient-user@jakarta.apache.org
> >>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=A8) but so far I have not seen any effect.
> >>
> >>Thanks,
> >>Aaron
> >>
> =
>>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: =
httpclient-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: =
httpclient-user-help@jakarta.apache.org
> >
> >
> >
> >
> >
> > =
---------------------------------------------------------------------
> > To unsubscribe, e-mail: =
httpclient-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: =
httpclient-user-help@jakarta.apache.org
> >
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: =
httpclient-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org