PM61617: CONNECTIONRESPONSETIMEOUT SET FROM 3420 - 3597 SECONDS CAUSES THE REQUESTS IN SERVANT TO TIMEOUT EARLY.

Fixes are available

APAR status

Closed as program error.

Error description

For the ConnectionResponseTimeout set from  3420 - 3597 seconds.
the requests in servants will timeout much earlier( in terms of
few seconds) due to  possible boundary condition issue with
respect to how timers from  3420 - 3597 seconds are handled.

Local fix

Use a time out value outside of the following range: 3420 - 3597
seconds.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Native alarms for dispatch timers may   *
*                      expire very early.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A subset of native timers have an optimized timer
implementation that shares "traditional" alarms across small
intervals to cut down on the large number of registered
"traditional" alarms.   The optimized timer implementation
is exposed to a scheduling delay in the "traditional" timer
support.  This causes a newly scheduled optimized timer to
share a "traditional" alarm that has already expired, but has
not removed its association to an optimized timer interval.
This association of a new optimized timer with an expired
"traditional" alarm causes the new alarm to expire prematurely.
This only affects timeout values at the edge of the allowed
timer values using the optimized timer implementation; which is
between 3420 - 3597 seconds.
The customer has observed premature timer pops from 19 seconds
to 104 seconds for a set timer value of 3595 seconds.
The native optimized timer support is used for: TCP Read,
Write, and Inactivity timers; Local Comm Asynchronous read; WLM
Dispatch timers (ex., ConnectionResponseTimeout/
protocol_http_timeout_output), and WLM Queue Percent timers.

Problem conclusion

Code has been modified in the scheduling area of the
"traditional" timer support to avoid the boundary problems
within the optimized timer support.

Also, code has been modified in the optimized timer support to
improve its sensitivity to scheduling delays for expired
"traditional" timers.

APAR PM61617 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.25 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM61617
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-03-30
Closed date
2012-04-24
Last modified date
2012-11-02

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

R700 PSY UK81738
UP12/10/04 P F210

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM61617: CONNECTIONRESPONSETIMEOUT SET FROM 3420 - 3597 SECONDS CAUSES THE REQUESTS IN SERVANT TO TIMEOUT EARLY.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UK81738

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?