On Aug 4, 11:27am, xuelei@oracle.com (Xuelei Fan) wrote:
-- Subject: Re: RFR 8052412: Too many DNS requests for KDC setttings
| On 8/4/2014 11:25 AM, Wang Weijun wrote:
| >
| > On Aug 4, 2014, at 11:14, Xuelei Fan wrote:
| >
| >> It's not common but the DNS records of KDC may be updated. T
On 8/4/2014 11:25 AM, Wang Weijun wrote:
>
> On Aug 4, 2014, at 11:14, Xuelei Fan wrote:
>
>> It's not common but the DNS records of KDC may be updated. This update
>> may introduce regression if the DNS record get updated. Is it possible
>> to support cache timeout in order to mitigate the im
On Aug 4, 2014, at 11:14, Xuelei Fan wrote:
> It's not common but the DNS records of KDC may be updated. This update
> may introduce regression if the DNS record get updated. Is it possible
> to support cache timeout in order to mitigate the impact?
Are you OK with using the TTL value in the
It's not common but the DNS records of KDC may be updated. This update
may introduce regression if the DNS record get updated. Is it possible
to support cache timeout in order to mitigate the impact?
Config.java:
1207 private static Map> dnsCache =
1208 Collections.s
Hi Xuelei
Are you OK with the code change? The updated webrev is now at
http://cr.openjdk.java.net/~weijun/8038089/webrev.02/
Comparing to the last version. there are some comment changes and emptying
refs.allowed. The only major change is that the ServiecLoader now uses system
class loader.
Please review the code change at
http://cr.openjdk.java.net/~weijun/8052412/webrev.00
The original code queries DNS server every time the getKDCList() method is
called. On the other hand, if the KDC info is written inside a krb5.conf file,
it is never re-read (or for each login when the JAAS
