Oracle 9i Servlets Test

This test reports the performance metrics pertaining to the servlets deployed in an Oracle 9i AS instance. In order to enable users to easily manage and monitor servlets, the eG Enterprise provides the Click Here hyperlink, which when clicked allows users to add, modify, or delete servlet groups. Note that by default eG Enterprise monitors only those servlets that are part of a group.

Target of the test : An Oracle 9i Application Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every servlet group configured or for every discovered servlet (as the case may be) .

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


In the Port text box, it is recommended that you provide the port at which the OPMN (Oracle Process Manager and Notification) process of the Oracle application server instance listens. To know at which port OPMN listens, click on the Ports tab in the following URL: http://<oraHttpServerIP>:<OraHttpServerport>. This tab lists the port numbers that were assigned to the services executing on the Oracle application server. The port number displayed against the Oracle notification server request port entry is the OPMN port, and the same should be specified in the Port text box.


The absolute path of the directory in which the Oracle 9i application server has been installed.


By default, eG Enterprise allows administrators to configure JSP groups using the eG administrative interface, and reports metrics pertaining to every group so created. Accordingly, by default, AutoDiscovery is set to No. If you want JSPs to be discovered and monitored automatically, then select the Yes option against AutoDiscovery. When this is done, the eG agent automatically discovers all the JSPs on the server, and reports one set of measures for every JSP so discovered.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Threads for servlet

Indicates the current number of threads servicing this servlet.


If a majority of the threads/processes are in use simultaneously to serve requests for a specific servlet, this may be indicative of a problem with a specific servlet or one of the components used by it. Alternatively, a slowdown of the application server may also cause the requests that are simultaneously executing to increase for all servlets.

Requests completed

Indicates the rate of calls to the service() method.


A very high value for this measure indicates that the servlet has been accessed many times.

Avg request process time

Indicates the average time spent in servicing the servlet during the last measurement period.


Comparing the request processing time across servlets, an administrator can determine which servlet(s) can be a performance bottleneck. An increase in response time of a servlet with load, could indicate a design problem with the servlet - eg., use of a non-optimal database query, database connection pool shortage, contention for shared resources, etc.

Max request process time

Indicates the maximum time spent on a servlet’s service() call.