Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8154304

NullpointerException at LdapReferralException.getReferralContext

    Details

      Backports

        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

          Issue Links

            Activity

            Hide
            coffeys Sean Coffey added a comment -
            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.
            Show
            coffeys Sean Coffey added a comment - 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.
            Hide
            hgupdate HG Updates added a comment -
            URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/e2b04e57b51a
            User: coffeys
            Date: 2016-04-16 12:15:08 +0000
            Show
            hgupdate HG Updates added a comment - URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/e2b04e57b51a User: coffeys Date: 2016-04-16 12:15:08 +0000
            Hide
            hgupdate HG Updates added a comment -
            URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/e2b04e57b51a
            User: lana
            Date: 2016-04-20 17:52:51 +0000
            Show
            hgupdate HG Updates added a comment - URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/e2b04e57b51a User: lana Date: 2016-04-20 17:52:51 +0000

              People

              • Assignee:
                coffeys Sean Coffey
                Reporter:
                shadowbug Shadow Bug
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: