Multiple Unexpected Instances Of Httpd Process After Tunning MaxSpareThreads
(Doc ID 2577352.1)
Last updated on SEPTEMBER 11, 2024
Applies to:
Oracle HTTP Server - Version 11.1.1.9.0 to 12.2.1.3.0 [Release Oracle11g to 12c]Information in this document applies to any platform.
Goal
Very high number of instances of httpd process after tuning MaxSpareThreads to be the same value as MinSpareThreads in the mpm_worker_module
After adjusting OHS to the following settings, a large number of httpd processes are running:
ServerLimit 128
StartServers 32
MinSpareThreads 1024
MaxSpareThreads 1024
ThreadLimit 72
ThreadsPerChild 32
MaxClients 4096
MaxRequestsPerChild 10000
AcceptMutex fcntl
LockFile "${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}/http_lock"
Previous settings where the issue was not present
ServerLimit 128
StartServers 32
MinSpareThreads 1024
MaxSpareThreads 2048
ThreadLimit 72
ThreadsPerChild 32
MaxClients 4096
MaxRequestsPerChild 10000
AcceptMutex fcntl
LockFile "${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}/http_lock"
Is it acceptable to set the MinSpareThreads and MaxSpareThreads to the same value?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |