IBM Support

PI78493: SERVLET CONTAINER INITIALIZATION CAN FAIL ON SERVER CREATED FROM TEMPLATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you have an application that works on a single
    appserver in a cell and then duplicate that server from a
    template of the original server, the application does not
    initialize correctly.  Servlet Container Initialization
    messages do NOT appear in the SystemOut.log.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who have created a new application   *
    *                  server from a template.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Servlet container initializers might    *
    *                      not be invoked on a server made from    *
    *                      a server template.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For an application deployed to an application server which is
    present in a federated topology, the server can be duplicated
    by creating a template of the server then creating a new
    server using the server template. Then modules may be mapped to
    the new server.  When starting the application on the duplicate
    server, the web container might fail to locate servlet
    container initializers of the module.  The initializers will
    not be invoked, and the application will not function
    correctly.
    For example, for a module which uses the Spring Framework,
    servlet container initializers are expected to display
    messages similar to the following in the SystemOut log.  When
    the problem occurs, these initializations messages are not
    displayed:
    [2/7/17 7:23:34:802 CST] 00000146 SystemOut     O 07:23:34.802
    [Default : 2] INFO  com.ibm.ws.webcontainer.webapp -
    SRVE0292I: Servlet Message -
    [APPLICATION#webModule.war]:.Initializing Spring embedded
    WebApplicationContext
    [2/7/17 7:23:34:802 CST] 00000146 SystemOut     O 07:23:34.802
    [Default : 2] INFO
    org.springframework.web.context.ContextLoader - Root
    WebApplicationContext: initialization completed in 1334 ms
    [2/7/17 7:23:35:829 CST] 00000146 SystemOut     O 07:23:35.829
    [Default : 2] INFO
    org.springframework.boot.web.servlet.ServletRegistrationBean -
    Mapping servlet: 'dispatcherServlet' to [/]
    [2/7/17 7:23:35:830 CST] 00000146 SystemOut     O 07:23:35.830
    [Default : 2] INFO
    org.springframework.boot.web.servlet.FilterRegistrationBean -
    Mapping filter: 'errorPageFilter' to: [/*]
    

Problem conclusion

  • The problem was fixed by an update to code which discovers
    servlet container initializers.  That code had not been fully
    enabled to access module classes.
    
    This problem is similar to the problem fixed by APAR PI27628.
    However, that APAR is in regards to the failure to discover
    servlet container initializers in shared libraries, which is a
    different problem.  See
    http://www-01.ibm.com/support/docview.wss?uid=swg1PI27628.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.12 and 9.0.0.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

    PI78493

  • 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

    2017-03-20

  • Closed date

    2017-04-05

  • Last modified date

    2017-04-05

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021