JDK-6442088 : Change default DNS caching behavior for code not running under security manager
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 6
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: other
- CPU: unknown
- Submitted: 2006-06-22
- Updated: 2017-05-16
- Resolved: 2006-08-05
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b95Fixed  |
Description
Our current default DNS caching behavior is to cache all entries forever. This causes problems for long running applications when changes to DNS occur.
Comments
|