Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
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
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
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
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
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
WebSphere Application Server traditional 9.0.5.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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
mod_zos_cmds incorrectly reports the number of lingering close connections as zero. This is because mod_zos_cmds counts the number of threads in the lingering close state instead of counting the number of connections.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM HTTP Server (powered by * * Apache) on z/OS. * **************************************************************** * PROBLEM DESCRIPTION: mod_zos_cmds incorrectly reports the * * number of lingering close connections * * as zero. * **************************************************************** * RECOMMENDATION: * **************************************************************** mod_zos_cmds incorrectly reports the number of lingering close connections as zero. This is because the lingering close state is a state of a connection and not a thread, but the number of threads in the lingering close state are counted. Instead, the number of connections in the lingering close state should be counted.
Problem conclusion
mod_zos_cmds was updated to report the number of connections in the lingering close state instead of the number of threads. This fix is targeted for IBM HTTP Server fix packs: - 9.0.0.4
Temporary fix
Comments
APAR Information
APAR number
PI73951
Reported component name
WAS IHS ZOS
Reported component ID
5655I3510
Reported release
90P
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-19
Closed date
2016-12-20
Last modified date
2017-01-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 IHS ZOS
Fixed component ID
5655I3510
Applicable component levels
R90P PSY
UP
Document Information
Modified date:
03 May 2022