IBM Support

PI28223: NULLPOINTEREXCEPTION IN JNDINESTEDFRAMEWORKSUPPORT (JNDI LOOKUP)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A NullPointerException occurring when performing an
    InitialContextlookup operation:
    
    java.lang.NullPointerException
     at
    com.ibm.ws.eba.app.runtime.services.internal.JNDINestedFramework
    Support.augmentEnvironment (JNDINestedFrameworkSupport.java:69)
     at
    org.apache.aries.jndi.AugmenterInvokerImpl.augmentEnvironment(Au
    gmenterInvokerImpl.java:48)
     at
    org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitia
    lContext(OSGiInitialContextFactoryBuilder.java:42)
     at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.j
    ava:695)
     at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav
    a:318)
     at
    javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContex
    t.java:346)
     at javax.naming.InitialContext.lookup(InitialContext.java:422)
    

Local fix

  • Not Applicable
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile - JMX                *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException during JNDI lookup *
    *                      from JMXConnectorFactory.connect        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    javax.management.remote.JMXConnectorFactory.connect causes a
    JNDI lookup to take place. This is intercepted by JNDI code that
    assumes an OSGi bundle context is available. In the JMX case,
    there is no context and so a NullPointerException occurs
    

Problem conclusion

  • The JNDI code has been updated to check for the existence of a
    bundle context before using it.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.6.  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

    PI28223

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-22

  • Closed date

    2015-04-22

  • Last modified date

    2015-04-22

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022