IBM Support

PM83576: SSL-ENABLED LDAP SERVER FAILED TO LOOKUP WITH CLASSNOTFOUNDEXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an SSL-enabled LDAP server is specified in the server.xml,
    any LDAP lookup will fail with the following exception:
    
    FFDC1015I: An FFDC Incident has been created:
    "javax.naming.CommunicationException: <ldaphost>:636
    [Root exception is java.lang.ClassNotFoundException:
    com.ibm.ws.security.registry.ldap.LdapSSLSocketFactory]
    com.ibm.ws.security.registry.ldap.internal.LdapRegistry 1169"
    
    Caused by: java.lang.ClassNotFoundException:
    com.ibm.ws.security.registry.ldap.LdapSSLSocketFactory
     at com.ibm.ws.classloading.internal.UnifiedClassLoader.
               findClass(Un ifiedClassLoader.java:52)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at com.sun.jndi.ldap.VersionHelper12.
               loadClass(VersionHelper12.java :57)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When Using LDAP SSL on Websphere        *
    *                      Application Server Liberty Profile, a   *
    *                      ClassNotFound error appears in the      *
    *                      traces.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When Using LDAP SSL on Websphere
    Application Server Liberty Profile, a
    ClassNotFound error appears in the
    traces and the user is not able to
    login.
    If the user uses LDAP only, the login will work
    correctly.
    

Problem conclusion

  • The error appears to exist only when using LDAP SSL. It was
    noted that there were some issues with the way the classes
    were loaded. The code has been modified to solve this
    problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.0. Please refer to the Recommended Updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83576

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-25

  • Closed date

    2013-06-03

  • Last modified date

    2013-06-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 June 2013