How do I collect Timing Diagnostics Data?
How do I collect Timing Diagnostics Data?
Timing diagnostic data is collected mainly during the deployment phase and occasionally during production environment phase. The data collected during Server runtime can be used to trace the cause of the problem. All diagnostic details collection are switched on and off simultaneously.
In the Explore panel, select Analyze > Server Diagnostics. The Server Diagnostic page is displayed. You can browse for a specific report and include it in the report list using the Load button.
The toolbar in Diagnostics home page displays the following options:
- Start: Starts the process of collecting diagnostics.
Note: Clicking Start for the first time displays a link to view current data.
- Stop: Stops collecting diagnostics data.
- Save: Saves the diagnostic data collected.
Note: The diagnostics data is temporary. Once the Server is stopped, the data is lost if it is not saved. The standard Save option does not save diagnostic data.
- Refresh: Refreshes the page. Displays the Server Diagnostics Report page.
Note: The standard Refresh button does not refresh the page.
- Trash: Deletes the selected item.
- Close: Closes the diagnostics window.
Click Start. A link to View current data is displayed. Click this link to view diagnostic details in Server.
The following timing diagnostics details are available on the home page:
- Transactions: Diagnostics for transactions committed and rolled back.
- Datasources: Time taken to connect to the datasources for the applications running on the Server.
- Applications: Application modules.
How do I collect Timing Diagnostics for Transaction?
A J2EE-based application server supports infrastructural services such as transactions. This is used by deployed application components for activities detached from business logic. Transaction service on the Server is based on Java Transaction API (JTA) 1.0.1 specification.
To ensure optimal performance and availability of applications, it is necessary to obtain diagnostic data on transaction response times. To obtain timing diagnostics data for transactions occurring at Server run time:
- Select Transactions from the diagnostics home page or the Explore panel. It displays the following details for the selected MBean:
Table 1: Transaction Diagnostics page
| Name | Description |
|---|
| Total Transaction Commit (ms) | Overall time taken to commit all the transactions. |
| Total Transactions Rollback (ms) | Overall time taken for transactions to rollback. |
- Click the MBean to view the diagnostics summary by task. For each task, the data on total number of hits, average time taken, and the cumulative time taken to serve the requests is collected and displayed. This diagnostic data is used to construct a histogram to simplify interpretation.
- Click any task to view the method name, package, module type, number of hits, average time taken to finish a transaction, cumulative time taken to complete a particular transaction, and a histogram based on the data available for the selected task.
How do I collect Timing Diagnostics for Datasources?
Server diagnostics provide information on datasource availability, historic information on capacity of database resources, sends alerts, and enables you to drill down to the problem. This simplifies the process of resolving performance issues.
- Select Datasources from the home page or from the Explore panel to view the datasource diagnostics. It gives the following details:
Table 2: Datasource Diagnostics
| Field | Description |
|---|
| Datasources | List of the datasource names accessed to run a particular application. |
| Total Wait Time to Obtain Conn (ms) | The time required to connect to the datasource. |
- Select the required datasource. The name and type of datasource and various datasource task details, such as the methods accessed, hits, average time taken to complete a particular task, and the cumulative time taken to serve the total number of requests is displayed.
Note: In addition to these tasks, various prepared statements for the current data source are also listed.
- Click any task to view the method name, package, module type, number of hits, average time taken to finish a transaction, cumulative time taken to complete a particular transaction, and a histogram based on the data available for the selected task.
How do I collect Timing Diagnostics for Applications?
It is important to monitor applications to detect performance degradation issues and solve them. Server enables the administrator to monitor a complex and distributed application environment. This creates a highly efficient and well managed system.
- Select Applications from the home page or from the Explore panel. All applications that are deployed on the Server are listed.
- Select an application to view the application modules.
- Select a war or jar module:
- Selecting a war displays the application name, module name, servlets under the selected module, and the service time for each method.
- Selecting a jar displays details about the application and module name, beans involved along with the time taken for activation, passivation, to load, store data, and to obtain and release a lock.
- Select the required component to view details such as application name, module name, name of the component, and type of the component.
Note: For a war module, the component is of servlet type. For a jar module the component is of bean type. In addition to the standard tasks, application specific business methods are also listed.
- Select a task to view the number of hits, the average and cumulative time taken to complete the task, along with a histogram based on the available data.
Related Topics:
| 
