Oracle HTTP Process Test

After Oracle HTTP Server is started, it is ready to listen for and respond to HTTP(S) requests. Oracle HTTP Server provides functionality that allows it to terminate as a single unit if the parent process fails. The parent process is responsible for starting and stopping all the child processes for an Oracle HTTP Server instance. The failure of the parent process without first shutting down the child processes leaves Oracle HTTP Server in an inconsistent state that can only be fixed by manually shutting down all the orphaned child processes. Until all the child processes are closed, a new Oracle HTTP Server instance cannot be started because the orphaned child processes still occupy the ports the new Oracle HTTP Server instance must access.

This test monitors and reports if all of the Oracle HTTP Server child processes are shut down, leaving the ports open for a new Oracle HTTP Server instance. The administrators can look at the reported metrics like uptime and IsRestarted to make sure that server process is running efficiently?

Target of the test : An Oracle HTTP Server 12c

Agent deploying the test : An External Agent or internal Agent

Outputs of the test : One set of results for every Oracle HTTP Server monitored

Configurable parameters for the test



Test period

How often should the test be executed.


The IP address of the Oracle HTTP Service.


The port number through which the Oracle HTTP Server 12c communicates. The default port is 7777.


By default, the Oracle HTTP Server is SSL-enabled. Accordingly, the SSL flag is set to Yes by default

Admin Port

Admin port details can be found in configuration file. The default port is 9999.

Measurements made by the test



Measurement Unit



Indicates the uptime of the server


If the service has been up for very long it might need restart to clear the ports and memory which will lead to improved performance.

Is Restarted

Indicates whether the server restarted