Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Each instance of the rotatelogs program referenced in httpd.conf uses two address spaces.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM HTTP Server users on z/OS with * * rotatelogs configured * **************************************************************** * PROBLEM DESCRIPTION: rotatelogs on z/OS is using an extra * * address space per instance * **************************************************************** * RECOMMENDATION: Apply this fix if using rotatelogs for IBM * * HTTP Server on z/OS * **************************************************************** On z/OS, rotatelogs had to be launched by a /bin/sh wrapper which used an additional address space.
Problem conclusion
rotatelogs can now be launched without being wrapped by /bin/sh which saves an address space per piped logger instance. This global behavior is activated by the native environment variable IHS_PIPED_LOGGER_NO_SHELL being set to any value. Without the new native environment variable IHS_PIPED_LOGGER_NO_SHELL, SIGTERM is not sent to rotatelogs. With IHS_PIPED_LOGGER_NO_SHELL, SIGTERM will be seen during shutdown and trigger a warning: CEE5205S. A new -T flag for rotatelogs has been added to ignore SIGTERM. This fix is targeted for IBM HTTP Server fix packs: - 7.0.0.43 - 8.0.0.13 - 8.5.5.10
Temporary fix
Comments
APAR Information
APAR number
PI57543
Reported component name
WAS IHS ZOS
Reported component ID
5655I3510
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-19
Closed date
2016-03-21
Last modified date
2016-04-20
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
R700 PSY
UP
Document Information
Modified date:
28 April 2022