IBM Support

PI81309: With Liberty Dynamic Routing, adding a cluster member to a collective might cause the web server plug-in to segfault.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a cluster member is added to a collective, if the
    applications in the cluster member are receiving a large
    number of requests, there is a possibility that the plugin
    will produce a segfault when one of the first few requests
    to the new cluster member completes. A core file may be
    produced if the web server is configured for it.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the Dynamic Routing feature of IBM *
    *                  WebSphere Application Server Liberty        *
    ****************************************************************
    * PROBLEM DESCRIPTION: With Liberty Dynamic Routing, adding a  *
    *                      cluster member to a collective might    *
    *                      cause the web server plug-in to         *
    *                      segfault.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a cluster member is added to a collective, if the
    applications in the cluster member are receiving a large number
    of requests, there is a possibility that the plugin will produce
    a segfault when one of the first few requests to the new cluster
    member completes. A core file may be produced if the web server
    is configured for it.
    

Problem conclusion

  • When a cluster member is started for the very first time, there
    could be a short period of time between when the server is
    started, and when the server becomes a member of the cluster.
    Requests that are sent to the new cluster member that arrive
    when the server is not a member of the cluster and complete when
    the server is a member of the cluster will cause a segfault in
    the Web Server plugin. We have added code to handle the case
    where a request arrives when a server is not in a cluster and
    completes when the server is in a cluster.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 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

    PI81309

  • 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-05-09

  • Closed date

    2017-05-18

  • Last modified date

    2018-08-20

  • 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

  • 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":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021