JDK-8154304 : NullpointerException at LdapReferralException.getReferralContext
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-04-15
  • Updated: 2016-07-21
  • Resolved: 2016-04-16
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.
JDK 7 JDK 8 JDK 9
7u101Fixed 8u102Fixed 9 b115Fixed
Related Reports
Relates :  
Description
[2016-04-13T20:49:41.008-05:00] [wls_oam1] [ERROR] [LXXX-60176]
[oracle.ods.virtualization.engine.backend.jndi.adapter1] [tid:
[ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default(self-tuning)'] [userId: <anonymous>] [ecid:fxxx8000-000000000000018e,0] [APP:oam_server#11.1.2.0.0] JNDI exception: java.lang.NullPointerException.[[
java.lang.NullPointerException
at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:92)
at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:150)
at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:128)
at oracle.ods.virtualization.engine.backend.jndi.JNDIEntrySet.handleReferral(JNDIEntrySet.java:587)

A new NPE after addressing an earlier one via JDK-8149450
Comments
As per RFC document, "at least one URI MUST be present in the Referral." No URI field is given from LDAP data stream. We're dealing with a non-compliant response and JDK is hitting new boundary conditions as a result. Should find out fromLDAP application team if they believe the response that the JDK is trying to process is in breach of RFC 4511 ��4.1.10 ? I can have the JDK handle the issue but perhaps the JDK should throw a general NamingException back to application rather than an LDAPReferralException.
15-04-2016