Additional httpd.worker Processes Created Which Cause Problems with System Accessibility

(Doc ID 2254160.1)

Last updated on APRIL 12, 2017

Applies to:

Oracle Transportation Management - Version 6.4.1 and later
Information in this document applies to any platform.


On system startup typically there are three or four "httpd.worker" processes launched.

Doing a ps -ef | grep worker will show these among other non-OTM threads

otm641 8528 1 0 Mar22 ? 00:00:09 /u01/bea_12.1.3/ohs/bin/httpd.worker -k start -f /u01/bea_12.1.3/user_projects/domains/otmweb/config/fmwconfig/components/OHS/instances/otm641/httpd.conf
otm641 8533 8528 0 Mar22 ? 00:00:04 /u01/bea_12.1.3/ohs/bin/httpd.worker -k start -f /u01/bea_12.1.3/user_projects/domains/otmweb/config/fmwconfig/components/OHS/instances/otm641/httpd.conf
otm641 8543 8528 0 Mar22 ? 00:00:10 /u01/bea_12.1.3/ohs/bin/httpd.worker -k start -f /u01/bea_12.1.3/user_projects/domains/otmweb/config/fmwconfig/components/OHS/instances/otm641/httpd.conf
otm641 8547 8528 0 Mar22 ? 00:00:09 /u01/bea_12.1.3/ohs/bin/httpd.worker -k start -f /u01/bea_12.1.3/user_projects/domains/otmweb/config/fmwconfig/components/OHS/instances/otm641/httpd.conf

This count is typically stable over time, but there is some activity that triggers growth to over 100 worker processes. When this occurs it makes the server unresponsive to User logins. Clients reporting this issue have noticed these additional processes may need to be manually "killed" before a normal restart returns the system to functioning state.


The OHS install was created on a NFS mount.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms