IBM Support

PI51841: Request timing can accidently remove an executing request from t he active request list

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Request timing maintains a list of active requests. A
    request handled by the web container is added to the list
    when the web container receives the request and is removed
    from it when the request completes.
    
    When there are long running requests, request timing code
    can accidently remove an executing request from the active
    request list. This could potentially result in that request
    not getting monitored.
    
    Example,
    Lets say that a request takes 5 mins to execute.
    Administrator may have removed the requestTiming feature and
    re-enabled it. We would be nulling out the request at the
    index the original request was using, not realizing that
    number was only valid before the activeRequests was cleared.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile - Debug/Tracing      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Request timing can accidently remove a  *
    *                      running request from the active request *
    *                      list.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Request timing maintains a list of active requests. It uses the
    active list to monitor running requests. A request handled by
    the web container is added to the list when the web container
    receives the request and is removed from it when the request
    completes. When there are long running requests, request timing
    code can accidentally remove a running request from the active
    request list before it completes. This could potentially result
    in that request not getting monitored.
    

Problem conclusion

  • Code was modified to the check that the running request is only
    removed on its completion. Any other condition that triggers the
    request removal is ignored.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.9.  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

    PI51841

  • 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

    2015-11-04

  • Closed date

    2015-11-09

  • Last modified date

    2015-11-09

  • 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:
30 November 2021