Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
64-bit Microsoft Windows Operating Systems require more space for each 32-bit IBM HTTP Server thread than 32-bit Microsoft Windows Operating Systems. This can result in available memory being exceeded for configurations using a very high ThreadsPerChild value.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM HTTP Server on a 64-bit * * Microsoft Windows server with high * * ThreadsPerChild values (approximately * * 2000). * **************************************************************** * PROBLEM DESCRIPTION: Available processing threads are more * * limited on 64-bit Microsoft Windows * * servers due to higher memory use per * * thread. * **************************************************************** * RECOMMENDATION: Apply this fix if you need to use high * * ThreadsPerChild values for IBM HTTP Server * * on a 64-bit Microsoft Windows server. * **************************************************************** The use of large numbers of IBM HTTP Server threads is more limited on a 64-bit Microsoft Windows server.
Problem conclusion
IBM HTTP Server on 64-bit Microsoft Windows can now provide more threads by use of an alternate httpd-la.exe executable that is Large Address Aware. In order to use this alternate executable, you must either modify the existing Windows service to use httpd-la.exe, or create a new Windows service that uses httpd-la.exe for the runtime and use it instead of the existing service. A new Windows service for the executable can be created by invoking it such as: httpd-la.exe -k install -n "IBM HTTP Server V8 LA". This fix is targeted for IBM HTTP Server fix packs: - 8.0.0.9 - 8.5.5.2
Temporary fix
Comments
APAR Information
APAR number
PI04922
Reported component name
IBM HTTP SERVER
Reported component ID
5724J0801
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-10-28
Closed date
2014-01-08
Last modified date
2014-01-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
IBM HTTP SERVER
Fixed component ID
5724J0801
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
07 September 2022