Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
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
After raising ThreadsPerChild or MaxClients, the server reports following error: (11)Resource temporarily unavailable: apr_thread_create: unable create worker thread
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM HTTP Server 9.0 on Linux * **************************************************************** * PROBLEM DESCRIPTION: Thread creation errors may occur if * * the ulimit -n value is not large * * enough for the ThreadsPerChild setting * **************************************************************** * RECOMMENDATION: Apply this fix if using IBM HTTP Server * * 9.0 on Linux * **************************************************************** If the current soft limit for RLIMIT_NPROC looks to be less than MaxClients (MaxRequestWorkers), raise it to the corresponding hard limit at startup.
Problem conclusion
IBM HTTP Server will now automatically raise ulimit -n if needed to accomodate larger ThreadsPerChild values. This fix is targeted for IBM HTTP Server fix packs: - 9.0.0.2
Temporary fix
Comments
APAR Information
APAR number
PI70022
Reported component name
IBM HTTP SERVER
Reported component ID
5724J0801
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-03
Closed date
2016-11-03
Last modified date
2016-11-03
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
R900 PSY
UP
Document Information
Modified date:
07 September 2022