IBM Support

PI76979: TIMING WINDOW WHERE TIMERS ARE NOT CALCULATED CORRECTLY

Fixes are available

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A server terminated with an EC3/04130007 http timeout that was
    less than the value specified for:
    
    protocol_http_timeout_output
    and
    protocol_https_timeout_output
    
    The
    BBOO0327I HTTP REQUEST TIMEOUT
    and time of the abend show the timeout doesn't match the
    configured variables.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and V9.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      timers expire too early or too          *
    *                      late.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Timers for request dispatch, WLM queue percent, TCP
    read, TCP write, and Local Comm async read, "may" be set to an
    incorrect value which would lead to either the timer requests
    expiring early or late.
    The exposure to his problem occurs after a Server has been
    running for 11 days, and every 10 days after, and lasts for at
    most 1 hour.
    Timers set for less than 36 minutes may be delayed by 27
    minutes during this exposure.
    Timers set for 36 to 59 minutes may expire from 1 to 23
    minutes.
    This problem was reported for a server with a setting of a
    request dispatch timer of 35 minutes (ex.
    protocol_http_timeout_output=2100).  The Server starts a few
    different timers based on this setting.  In the controller it
    will set a timer based on the request dispatch timer plus an
    additional 85 seconds.  If this timer pops and the request
    is still active in the Server, it will timeout the request with
    a BBOO0327I timeout message and may terminate the related
    servant with an ABENDSEC3 RSN=04130007.  For this 36 minute and
    25 second timeout value it expired in 25 seconds.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI76979

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-21

  • Closed date

    2017-03-08

  • Last modified date

    2017-03-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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

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

Document Information

Modified date:
24 November 2021