OC4J Performance Metrices in SOA Suite Application Server
I have collected below brief information about some of the performance metrices used in OC4J monitoring in SOA Suite . This is a brief idea. Have a look :-
CPU (%)
Description: The percentage of the CPU currently being used by the OC4J instance, or--on the JVM Metrics page--the selected Java Virtual Machine (JVM).
User Action: Use this metric to determine how much of the CPU is in use by the OC4J instance or JVM. If you encounter consistent high readings for this metric, try to isolate the problem by monitoring individual applications and services that are running on the OC4J instance. If no problems are found, consider obtaining additional hardware resources or load balancing solutions.
Memory (MB)
Description: Indicates how much of your total physical memory is in use by the current OC4J instance, or--on the JVM Metrics page--by the selected Java Virtual Machine (JVM).
User Action: Use this metric to monitor memory use by the OC4J instance or JVM. Compare this with heap usage and non-heap usage metrics available for the Java Virtual Machine. If you experience consistent high readings for this metric, investigate the memory usage of individual applications and services deployed to the OC4J instance. If no problems are found, consider additional hardware resources or load balancing solutions.
Heap Usage
Description: Each JVM has a memory heap that is created automatically when the Java virtual machine (JVM) is started. This memory heap is used by the JVM class instances and arrays. This metric Indicates how much of the JVM heap (in Megabytes) is currently in use.
User Action: This information can help you determine whether or not you need to adjust the JVM heap size. In extreme cases, if the heap usage exceeds the configured size of the heap, you can encounter java.lang.OutOfMemory errors.
Start Time
Description: The time the OC4J instance or the selected Web Service was started. If multiple JVMs are started at different times, the start time of the first JVM is shown (the longest running JVM).
User Action: None.
JDBC Usage Metrics
Active Sessions
Description: This metric displays the number of currently active sessions for the servlets and JSPs on this OC4J instance.
User Action: Use this metric, with the other Servlet/JSP metrics, to determine the load on the OC4J instance. If you are experiencing performance problems, monitor this metric for trends or spikes. A consistently high number of active sessions can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances.
Servlet and JSP - Active Requests
Description: In the context of the OC4J instance, this metric provides the number of requests currently being executed by all the servlets and JSPs on this OC4J instance. In the context of a selected JSP or servlet, this metric provides the number of requests currently being executed by the selected JSP or servlet.
User Action: Use this metric, with the other Servlet and JSP metrics, to determine the load on the OC4J instance. If you are experiencing performance problems, monitor this metric for trends or spikes. A consistently high number of active requests can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances.
Request Processing Time (seconds)
Description: The average amount of time in seconds that the Servlets and JSPs in this OC4J instance or JVM have spent processing requests since the OC4J server was started.
User Action: Use this metric to identify trends or sudden changes in the performance of the JSPs and servlets running on the OC4J instance or JVM. If the value of this metric increases over a period of time, investigate potential problems with individual applications or services on the OC4J server. If no problems are found, consider obtaining additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances or additional JVMs.
Requests per Second
Description: In the context of the OC4J instance or Java Virtual Machine (JVM), this metric provides the average number of servlet and JSP requests per second for all JSPs and servlets in the OC4J instance or JVM. In the context of a selected servlet or JSP, it provides the average number of requests per second for the selected servlet or JSP.
User Action: Use this metric, with the other Servlet and JSP metrics, to determine the load on the OC4J instance, JVM, or on a selected servlet or JSP. If you are experiencing performance problems, monitor this metric for trends or spikes. In the context of the OC4J instance or JVM, a consistently high rate of requests can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances or additional JVMs.
CPU (%)
Description: The percentage of the CPU currently being used by the OC4J instance, or--on the JVM Metrics page--the selected Java Virtual Machine (JVM).
User Action: Use this metric to determine how much of the CPU is in use by the OC4J instance or JVM. If you encounter consistent high readings for this metric, try to isolate the problem by monitoring individual applications and services that are running on the OC4J instance. If no problems are found, consider obtaining additional hardware resources or load balancing solutions.
Memory (MB)
Description: Indicates how much of your total physical memory is in use by the current OC4J instance, or--on the JVM Metrics page--by the selected Java Virtual Machine (JVM).
User Action: Use this metric to monitor memory use by the OC4J instance or JVM. Compare this with heap usage and non-heap usage metrics available for the Java Virtual Machine. If you experience consistent high readings for this metric, investigate the memory usage of individual applications and services deployed to the OC4J instance. If no problems are found, consider additional hardware resources or load balancing solutions.
Heap Usage
Description: Each JVM has a memory heap that is created automatically when the Java virtual machine (JVM) is started. This memory heap is used by the JVM class instances and arrays. This metric Indicates how much of the JVM heap (in Megabytes) is currently in use.
User Action: This information can help you determine whether or not you need to adjust the JVM heap size. In extreme cases, if the heap usage exceeds the configured size of the heap, you can encounter java.lang.OutOfMemory errors.
Start Time
Description: The time the OC4J instance or the selected Web Service was started. If multiple JVMs are started at different times, the start time of the first JVM is shown (the longest running JVM).
User Action: None.
JDBC Usage Metrics
Active Sessions
Description: This metric displays the number of currently active sessions for the servlets and JSPs on this OC4J instance.
User Action: Use this metric, with the other Servlet/JSP metrics, to determine the load on the OC4J instance. If you are experiencing performance problems, monitor this metric for trends or spikes. A consistently high number of active sessions can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances.
Servlet and JSP - Active Requests
Description: In the context of the OC4J instance, this metric provides the number of requests currently being executed by all the servlets and JSPs on this OC4J instance. In the context of a selected JSP or servlet, this metric provides the number of requests currently being executed by the selected JSP or servlet.
User Action: Use this metric, with the other Servlet and JSP metrics, to determine the load on the OC4J instance. If you are experiencing performance problems, monitor this metric for trends or spikes. A consistently high number of active requests can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances.
Request Processing Time (seconds)
Description: The average amount of time in seconds that the Servlets and JSPs in this OC4J instance or JVM have spent processing requests since the OC4J server was started.
User Action: Use this metric to identify trends or sudden changes in the performance of the JSPs and servlets running on the OC4J instance or JVM. If the value of this metric increases over a period of time, investigate potential problems with individual applications or services on the OC4J server. If no problems are found, consider obtaining additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances or additional JVMs.
Requests per Second
Description: In the context of the OC4J instance or Java Virtual Machine (JVM), this metric provides the average number of servlet and JSP requests per second for all JSPs and servlets in the OC4J instance or JVM. In the context of a selected servlet or JSP, it provides the average number of requests per second for the selected servlet or JSP.
User Action: Use this metric, with the other Servlet and JSP metrics, to determine the load on the OC4J instance, JVM, or on a selected servlet or JSP. If you are experiencing performance problems, monitor this metric for trends or spikes. In the context of the OC4J instance or JVM, a consistently high rate of requests can indicate the need for additional hardware resources or load balancing solutions, such as clustering multiple OC4J instances or additional JVMs.
Comments