IBM Support

PI17504: VMM THROWS NULLPOINTEREXCEPTION DURING LOGIN IF CONTEXTPOOL IS DISABLED

Fixes are available

7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After applying fixpack 31, users fails to login to applications
    anymore after sometime of first log-in when context pool for
    LDAP is disabled in federated repository.
    NullPointerException occurs when connecting to LDAP;
    
    --------------------------------------------
    [25.04.14 09:23:19:432 CEST] 000000ee exception
    com.ibm.websphere.wim.exception.WIMException <init>
    at com.ibm.ws.wim.ProfileManager.loginImpl
       (ProfileManager.java:3666 )
    at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod
       (ProfileManager.java:316)
    at com.ibm.ws.wim.ProfileManager.login(ProfileManager.java:424)
    
    >>>
    
    Caused by: java.lang.NullPointerException
    at com.ibm.ws.wim.adapter.ldap.LdapConnection.reCreateDirContext
      (LdapConnection.java:827)
    at com.ibm.ws.wim.adapter.ldap.LdapConnection.search
       (LdapConnection.java:3017)
    at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearch
       Cache(Ldap Connection.java:2962)
    at com.ibm.ws.wim.adapter.ldap.LdapConnection.search
       (LdapConnection .java:3152)
    --------------------------------------------
    

Local fix

  • This problem does not occur when context pool is enabled.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Virtual member manager (VMM) login      *
    *                      fails with NullPointerException if      *
    *                      contextPool is disabled in LDAP         *
    *                      configuration.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the contextPool is disabled in LDAP configuration of VMM,
    a login call fails with VMM. It typically happens if
    the ldapServerType is custom. While acquiring a lock for a
    semaphore the check was missing to see if the if Context pool
    is not enabled.
    

Problem conclusion

  • This fix checks the status of the context pool before
    acquiring the lock for the semaphore.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.4  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

    PI17504

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-08

  • Closed date

    2014-07-30

  • Last modified date

    2014-11-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI17504

Modified date: 03 November 2014