IBM Support

PI82621: HANDLE NPE AND EMIT SERVICABLE FAILURE MESSAGE WHEN PARSING SERVER ENDPOINT METADATA

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The application server throws a NulPointerException when
    parsing a server's endpoint configuration.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The server system log indicates         *
    *                      a NullPointerException occurred while   *
    *                      processing the serverindex              *
    *                      configuration.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a WebSphere Server process encounters a corrupt
    serverindex.xml descriptor (file), the Server emits to the
    system log an error message for the component that failed to
    acquire the serverindex information. It then emits the
    causal exception, but the causal exception rarely elaborates
    the corruption. For example:
    [20/03/16 15:10:12:395 GMT] 00000000 ContainerHelp E
    WSVR0501E: Error creating component
    com.ibm.ws.cluster.runtime.ProcessRuntimeImpl
    java.lang.NullPointerException
    at
    com.ibm.ws.runtime.config.ConfigObjectImpl.getValue(ConfigObject
    Impl.java:374)
    at
    com.ibm.ws.runtime.config.ConfigObjectImpl.getString(ConfigObjec
    tImpl.java:639)
    at
    com.ibm.ws.runtime.config.AbstractConfigObject.getString(Abstrac
    tConfigObject.java:36)
    at
    com.ibm.ws.runtime.component.EndPointMgrImpl.parseEndPoints(EndP
    ointMgrImpl.java:416)
    at
    com.ibm.ws.runtime.component.EndPointMgrImpl.parseServerIndex(En
    dPointMgrImpl.java:390)
    at
    com.ibm.ws.runtime.component.EndPointMgrImpl.parseServerIndex(En
    dPointMgrImpl.java:384)
    at
    com.ibm.ws.runtime.component.EndPointMgrImpl.getNodeEndPoints(En
    dPointMgrImpl.java:333)
    at
    com.ibm.ws.runtime.component.EndPointMgrImpl.getNodeEndPoints(En
    dPointMgrImpl.java:303)
    at
    com.ibm.ws.cluster.service.BuildLSDCluster.createLSDAddressList(
    BuildLSDCluster.java:328)
    at
    com.ibm.ws.cluster.runtime.ProcessRuntimeImpl.initialize(Process
    RuntimeImpl.java:332)
    This NullPointerException occurred because the
    serverindex.xml file declared partial information for an
    <endPoint> element, which is not obvious without further
    information.
    The serverindex configuration declares the endpoints used by
    the various Server processes in a node. Problems deriving from
    an invalid serverindex are typically fatal.  Symptoms include
    Server processes that do not start, or once started, are
    unable to communucate as designed. To decrease the time to
    service these problems APAR PI82621 enables the Server to emit
    three new error messages when it encounters a
    corrupt serverindex configuraton.
    1. WSVR0657E: The server failed to collect endpoint
    information for the {NODENAME} node because the serverindex
    references an endpoint that does not exist.
    The Server emits this message whenever the serverindex.xml
    file declares an endPointRefs attribute or <endPointRefs>
    element that references a NamedEndPoint not declared in the
    same file.
    The serverindex.xml file should not contain <endPointRef>
    elements.
    2. WSVR0658E: The server failed to collect endpoint
    information for the {NODENAME} node because the serverindex
    contains an <endPointRefs> element.
    The Server emits this message whenever serverindex.xml file
    declares both an <endPointRefs> element and an endPointRefs
    attribute that reference one or more NamedEndPoint.
    Again, the serverindex.xml file should not contain
    <endPointRef> elements.
    3. WSVR0659E: The server failed to collect endpoint
    information for the {NODENAME} node because the serverindex
    contains partial information about the {NAMEDENDPOINT}
    endpoint.
    The Server emits this message whenever serverindex.xml does
    not declare a valid <endPoint> element for the named endpoint.
    Service this problem by restoring the serverindex.xml file in
    the specified node to a previous version that is not corrupt.
    

Problem conclusion

  • Apply APAR PI82621 to enable the EndPointManager to emit
    serviceable error messages when it encounters an
    invalid serverindex.xml file in the node configuration.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.45, 8.0.0.14, 8.5.5.13, and 9.0.0.5.  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

    PI82621

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-06

  • Closed date

    2017-06-19

  • Last modified date

    2017-06-19

  • 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

  • R900 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI82621

Modified date: 19 June 2017