8323089: networkaddress.cache.ttl is not a system property

Reviewed-by: alanb, jpai, aefimov, dfuchs
This commit is contained in:
Daniel Jeliński 2024-02-12 07:54:48 +00:00
parent 2546afe2aa
commit efa071dd06
2 changed files with 8 additions and 8 deletions

View File

@ -1,5 +1,5 @@
/*
* Copyright (c) 1995, 2023, Oracle and/or its affiliates. All rights reserved.
* Copyright (c) 1995, 2024, Oracle and/or its affiliates. All rights reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
@ -194,8 +194,8 @@ import static java.net.spi.InetAddressResolver.LookupPolicy.IPV6_FIRST;
* caching. Likewise, a system admin can configure a different
* negative caching TTL value when needed or extend the usage of the stale data.
*
* <p> Three Java security properties control the TTL values used for
* positive and negative host name resolution caching:
* <p> Three Java {@linkplain java.security.Security security} properties control
* the TTL values used for positive and negative host name resolution caching:
*
* <dl style="margin-left:2em">
* <dt><b>networkaddress.cache.ttl</b></dt>

View File

@ -1,6 +1,6 @@
<!DOCTYPE HTML>
<!--
Copyright (c) 1998, 2023, Oracle and/or its affiliates. All rights reserved.
Copyright (c) 1998, 2024, Oracle and/or its affiliates. All rights reserved.
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
This code is free software; you can redistribute it and/or modify it
@ -260,14 +260,14 @@ successful or not, so that subsequent identical requests will not
have to access the naming service. These properties allow for some
tuning on how the cache is operating.</P>
<UL>
<LI><P><B>{@systemProperty networkaddress.cache.ttl}</B> (default: see below)<BR>
<LI><P><B>{@code networkaddress.cache.ttl}</B> (default: see below)<BR>
Value is an integer corresponding to the number of seconds successful
name lookups will be kept in the cache. A value of -1, or any other
negative value for that matter, indicates a &ldquo;cache forever&rdquo;
policy, while a value of 0 (zero) means no caching. The default value
is -1 (forever) if a security manager is installed, and implementation-specific
when no security manager is installed.</P>
<LI><P><B>{@systemProperty networkaddress.cache.stale.ttl}</B> (default: see below)<BR>
<LI><P><B>{@code networkaddress.cache.stale.ttl}</B> (default: see below)<BR>
Value is an integer corresponding to the number of seconds that stale names
will be kept in the cache. A name is considered stale if the TTL has expired
and an attempt to lookup the host name again was not successful. This
@ -276,7 +276,7 @@ tuning on how the cache is operating.</P>
A value of 0 (zero) or if the property is not set means do not use stale
names. Negative values are ignored.
The default value is implementation-specific.</P>
<LI><P><B>{@systemProperty networkaddress.cache.negative.ttl}</B> (default: {@code 10})<BR>
<LI><P><B>{@code networkaddress.cache.negative.ttl}</B> (default: {@code 10})<BR>
Value is an integer corresponding to the number of seconds an
unsuccessful name lookup will be kept in the cache. A value of -1,
or any negative value, means &ldquo;cache forever&rdquo;, while a
@ -284,7 +284,7 @@ tuning on how the cache is operating.</P>
</UL>
<P>Since these 3 properties are part of the security policy, they are
not set by either the -D option or the {@code System.setProperty()} API,
instead they are set as security properties.</P>
instead they are set as {@linkplain java.security.Security security} properties.</P>
<a id="Unixdomain"></a>
<H2>Unix domain sockets</H2>
<p>