IBM Support

PI27628: SERVLET CONTAINER INITIALIZATION CAN FAIL WHEN USING SHARED LIBRARIES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Servlet container initialization can fail when class
    information for the initializer classes is completed by classes
    in shared libraries.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Detection of Servlet Container          *
    *                      Initializers fails when initializer     *
    *                      superclasses are in shared libraries    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application which uses Servlet Container Initializers will
    fail when a Servlet Container Initializer uses a superclass or
    an interface which is in a shared library.
    No error message is displayed during Servlet Container
    Initializer detection and registration.  The failure will
    manifest as a failure of Servlet Container Initializers to
    function properly, usually, with the application failing to run
    one or more initializers.
    

Problem conclusion

  • The problem occurred because the class loader used for
    Servlet Container Initializer detection and registration did
    not always have access to shared libraries.  This resulted in
    a failure to fully expand the superclasses and interfaces of
    candidate servlet container initializer classes.  Because
    Servlet Container Initializer detection tests superclasses and
    interfaces of candidate classes, this resulted in failures to
    detect candidate classes as Servlet Container Initializers.
    
    The problem was fixed by updating the code which initializes
    the class loader which is used when detecting Servlet Container
    Initializers.  The class loader initialization has new steps
    which ensure that shared libraries are included in the class
    path.
    
    To ensure backwards compatibility, the code defaults
    to the previous behavior.  To enable the new behavior, in
    addition to installation of an interim fix or of a fix pack
    which includes the code changes, a java system property must
    be set with a "true" value, as follows:
    
    com.ibm.ws.ecs.force.context.classloader=true
    
    The java system property must be set on all application
    servers which are used to run the application which encounters
    the problem.  The application server must be restarted.  The
    application does not need to be redeployed.
    
    The java system property can be set on deployment manager
    nodes, but, is not required to be set on these nodes.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.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

    PI27628

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-14

  • Closed date

    2015-01-16

  • Last modified date

    2015-01-16

  • 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

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022