IBM Support

PH43914: PMI ASYNCCONTEXT RESPONSE TIME CANNOT BE SET

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In the console, follow the steps below
    
     Monitor and Tuning > Performance Monitoring Infrastructure
    (PMI) >
     Performance Monitoring Infrastructure (PMI) > server1 > Custom
    Monitor Level > Web Application
    
    
    At this two are disabled, select "Per servlet" and press the
    enable button, then "Per servlet" is not enabled and "Per URI"
    is enabled.
    
    [v][AsyncContext ResponseTime(Per servlet)] [Disabled]
    [ ][AsyncContext ResponseTime(Per URI)]     [Disabled]
     ->Press [To enable] button.
    [ ][AsyncContext ResponseTime(Per servlet)] [Disabled]
    [ ][AsyncContext ResponseTime(Per URI)]     [Enabled]
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: PMI Servlet AsyncContext Response Time  *
    *                      cannot be set using the Administrative  *
    *                      Console                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In the Administrative Console, under Monitor and Tuning >
    Performance Monitoring Infrastructure
    (PMI)> Custom Monitor Level > Web Application, the names for
    AsyncContext ResponseTime(Per servlet)and AsyncContext
    ResponseTime(Per URL) are the same -- they are both AsyncContext
    ResponseTime. When a user tries to enable the AsyncContext
    ResponseTime servlet statistic, the AsyncContext ResponseTime
    URL
    statistic is always enabled instead. This occurs because both
    stats
    are housed in the same map under the same ID, "AsyncContext
    ResponseTime".
    

Problem conclusion

  • The URL AsyncContext ResponseTime statistic ID has been
    changed to
    "URL AsyncContext ResponseTime" to reflect the difference
    between
    the two statistics, and to avoid duplicate IDs in the same
    statistic map.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.23 and 9.0.5.13. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH43914

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-08

  • Closed date

    2022-07-11

  • Last modified date

    2022-09-08

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

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

Document Information

Modified date:
08 September 2022