PM94198: TIMEOUTS MUST BE THE SAME FOR EVERY URL ON A SERVER

Fixes are available

APAR status

Closed as program error.

Error description

Improvement to Plugin for ServerIOTimeout and static file servin

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Currently, all URLs must follow the     *
*                      same ServerIOTimeout,                   *
*                      ServerIOTimeoutRetry, and handshake     *
*                      timeout rules. Also, there is no        *
*                      blacklist available for URL's not       *
*                      intended to be handled by the           *
*                      application server.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Under the current Plugin model, every URL must use the same
ServerIOTimeout, ServerIOTimeoutRetry, and Extended Handshake
/ 100 Continue timeout rules.  Not all URLs behave the same
and there may be a need to time out a request quicker, not
have every server retried, or even to skip routing the request
to
WAS.

Problem conclusion

Customers using IBM HTTP Server or Apache with this updated
plugin now have the ability to designate specific URLs that
will use a modified ServerIOTimeout, ServerIOTimeoutRetry, or
shortened-timeout for ExtendedHandshake or 100-Continues.
Whereas, other URLs will continue to use the values specified
within the Plugin-cfg.xml file.  Note:  When using the
websphere-shorten-handshake override, it is only a true value
"1".  The plugin will then use the ConnectTimeout value as the
wait time for the ExtendedHandshake or 100-Continue responses.

To define a URL based override, you will modify the
httpd.conf file using SetEnvIf directives.  Like the
properties available within the Plugin-cfg.xml file, both
websphere-serveriotimeout & websphere-serveriotimeoutretry can
accept the same values.

SetEnvIf Request_URI "\.jsp$" websphere-serveriotimeout=10
SetEnvIf Request_URI "\.jsp$" websphere-serveriotimeoutretry=-1
SetEnvIf Request_URI "\.jsp$" websphere-shorten-handshake=1

To process a URL locally in the Apache based server, overriding
the patterns in plugin-cfg.xml:

  SetEnvIf Request_URI "\.(jpe?g|gif|css|js)$" skipwas=1

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.8, 8.5.5.2.  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
PM94198
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-31
Closed date
2013-10-10
Last modified date
2015-04-30

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

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

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

Document Information

Modified date:
27 April 2022

Tips

PM94198: TIMEOUTS MUST BE THE SAME FOR EVERY URL ON A SERVER

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?