JDK-8154474 : Release Note: Improved exception handling for bad LDAP referral replies
- Type: Sub-task
- Component: core-libs
- Sub-Component: javax.naming
- Affected Version: 7u111,8u102,9
- Priority: P4
- Status: Closed
- Resolution: Delivered
- OS: generic
- CPU: generic
- Submitted: 2016-04-18
- Updated: 2022-06-14
- Resolved: 2016-08-29
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 7 | JDK 8 | JDK 9 |
|---|---|---|
| 7u111Resolved | 8u102Resolved  |
9Resolved |
Description
The JDK was throwing a NullPointerException when a non-compliant REFERRAL status result was sent but no referral values were included. With this change, a NamingException with message value of "Illegal encoding: referral is empty" will be thrown in such circumstances. See JDK-8149450 and JDK-8154304 for more details