How do I interpret Diagnostics?

How do I interpret Diagnostics?

How do I interpret Diagnostics?

Consider the following example of a bank application:

Start the Server.
Using Deploy Tool, open BankDesk.ear available at <install_dir>\server\samples\ejb11\BankDesk\ear\. Click Deploy to deploy the application.
On the Console, select Analyze > Server Diagnostics. It displays the Server Diagnostic home page.
Click Start on the tool bar. It displays a new link to View current data.
Open a browser and start the application by entering the URL as http://127.0.0.1:8181/bankWeb/bank.jsp. Create two accounts, 1111 and 2222 with initial balances of Rs. 5,000 each using the New Account tab. Then, using the Transfer tab, transfer Rs.1,000 from account number 1111 to 2222.
Click View Current Data. It displays the Diagnostics page.
Note: The application may run on the local or a remote server. Server collects diagnostic data for both cases. Click Refresh to view the diagnostic data for the request sent to Server.

How do I read Transaction Diagnostics?

Select Transactions. It displays the corresponding details. You can check for the nature and details of transactions. Click on the MBean to view the following details:

Table 1: Method descriptions for Transaction MBean

Method Name	Description
Transaction Commit	Implies that a transaction has been committed.
Transaction Heuristic Mixed	Implies that the transaction was not committed because of data corruption.
Total Transaction	Indicates the total number of transactions that have occurred.
Transaction Rollback	Implies that a transaction has rolled back.
Transaction Heuristic Rollback	Implies that the transaction was not committed because of some network problem. The database or resource is not affected by this rollback.
Transaction Set Rollback	Implies that the transaction was not committed because of a logic specified in the code.

You can select the Transaction Commit method from the list and study the drill down on the following page.

How do I read Datasource Diagnostics?

Selecting datasources displays the following details:

Table 2: Datasource details

Field	Options	Description
Module Name	-	Refers to the name of the deployed module.
JDBC Datasource	-	Displays the JDBC datasource details.
-	Datasources	Displays the JDBC datasource name.
-	Total wait time to obtain connection (ms)	Displays the total time required to get connected.

Click on a datasource name to view the following details:

Table 3: Datasource Diagnostics

Method	This value indicates the
wait Time To Obtain Conn	Time taken to obtain a connection from the resource pool.
waiting Thread Time	Time taken to wait for a connection from the pool. A requestor may need to wait for a connection because a new connection cannot be created due to the limitation of the pool size. Then, the requestor has to wait for one currently used connection to become available.
prep Stmt Obtained From Cache	Number of prepared statements that are retrieved from the cache.
new Conn Creation Freq	Number of times a new connection is created.
prep Stmt Created Afresh	Number of prepared statements that are created afresh. The ratio of this value and the prepStmtObtainedFromCache value can give you an indication if you need to change the value of the number-of-cached-prepared-statement tag in the server-config.xml file.
connection Use Time	Duration for which the connection is in use.
conn Available In Thread Context	Number of times an existing connection is made available to the requestor from the same transaction.

Selecting a method, for example, the connectionUseTime, displays a histogram for it.

How do I read Application Diagnostics?

Selecting Applications displays a list of deployed applications. Clicking an application, say BankDesk.ear, displays the type of the application and the components that make it.

Table 4: Application Diagnostic Details

Field	Options	Description
Type	-	Refers to the type of the deployed application. For example, J2EE application.
Components	-	Displays the wars and jars for the application.
-	Wars	Displays the Web modules for the selected application. For example, bankWeb.
-	Jars	Displays the Java modules for the selected application. For example, bankEJB.jar.

Reading Web Modules

Selecting the Web module displays the following details:

Table 5: Web Module Details

Field	Description
Module Name	Refers to the name of the selected Web module. Say, bankWeb.
Servlet	Displays the list of servlets for the module, along with the total time taken for the method.

Clicking on a Servlet name, say /transfer.jsp, displays details like the application name, module name, the servlet name, the task name, hits made for the particular task, and the average and cumulative time taken for the completion of the task.
Selecting the task name displays a histogram for the activity on the same, if there is sufficient data available.
Clicking the ‘+’ icon expands the tree and displays more details as below, while clicking the arrow icon collapses the tree view.

Reading jar Modules

Selecting the jar module displays the following details:

Table 6: jar module details

Field	Options	Description
Module Name	-	The name of the selected jar module, say bankEJB.jar.
Entity Bean	-	The details for the entity beans.
-	Beans	The name of the entity bean.
-	Total Activation Time (ms)	The total activation time for the entity bean in milliseconds.
-	Total Passivation Time (ms)	The total passivation time for the entity bean in milliseconds.
-	Total Load Time (ms)	The total load time for the entity bean in milliseconds.
-	Total Store Time (ms)	The total store time for the entity bean in milliseconds.
-	Total Locking Time (ms)	The total locking time for the entity bean in milliseconds.
Stateful Session Bean	-	The details for the stateful session beans.
-	Beans	The name of the stateful session beans.
-	Total Activation Time (ms)	The total activation time for the stateful session bean in milliseconds.
-	Total Passivation Time (ms)	The total passivation time for the stateful session bean in milliseconds.
Stateless Session Bean	-	The details for the stateless session beans.
-	Beans	The name of the stateless session beans.
Message Driven Bean	-	The details for the message driven beans.
-	Beans	The name of the message driven bean.
-	Time taken for MDBeans onMessage method call	The time taken for MDBs onMessage method call.

Reading Entity Beans

Selecting an entity bean name displays the following details:

Table 7: Reading Entity Beans

Task name	Time taken
create:java.lang.Long;double;java.lang.String;(BusinessMethod)	To execute the applications business method.
findByID:long;(BusinessMethod)	To execute the applications business method.
findAllAccounts:(BusinessMethod)	To execute the applications business method.
lockingTime	To obtain and release a lock by the bean.
postProcesingTime	To complete the tasks that are done after processing the actual business methods in the bean.
storeTime	To store data.
preProcessingTime	To complete the tasks that are done prior to processing the actual business methods in the bean.
getCustomer_name:(BusinessMethod)	To execute the applications business method.
loadTime	To load data.
activationTime	For activation.
riLockingTime	To lock a remote bean instance.
onPoolWaitingTime	To wait for getting a bean from the bean pool.
ejbActivateTime	To call the ejbActivate method.
beanGetTime	To get a bean from the bean pool.
creatingTime	To create a bean instance.
lockRowTime	To lock a row.
onCacheWaitingTime	To wait for getting a bean from the cache.
debit:double;(BusinessMethod)	To execute the applications business method.
getAccount_number:(BusinessMethod)	To execute the applications business method.
credit:double;(BusinessMethod)	To execute the applications business method.
getBalance:(BusinessMethod)	To execute the applications business method.
verifiedUpdateTime	Verify the updation of the bean.
activateLoadTime	To activate the load.
rollbackLoadTime	To rollback the load.
lockWaitingTime	To obtain a lock for the bean.
passivationTime	For passivation.

Selecting the task name displays a histogram for the activity on the same, if there is sufficient data available.

Reading Stateful Session Beans

Selecting a stateful session bean name displays the following details:

Table 8: Reading Stateful Session Beans

Task name	Time taken
createEntry:long;java.lang.String;double;(BusinessMethod)	To execute the applications business method.
createEntry:long;java.lang.String;double;(ActualMethod)	To execute the applications actual method.
create:(BusinessMethod)	To execute the applications business method.
preProcessingTime	To complete the tasks that are done prior to processing the actual business methods in the bean.
getLedgerRows:(BusinessMethod)	To execute the applications business method.
getLedgerRows:(ActualMethod)	To execute the applications actual method.
postProcesingTime	To complete the tasks that are done after processing the actual business methods in the bean.
onPoolWaitingTime	To wait for getting a bean from the bean pool.
beanGetTime	To get a bean from the bean pool.
aliveTime	For which the bean is in existence.
creatingTime	To create a bean instance.
ejbActivateTime	To call the ejbActivate method.
activationTime	For activation.
riLockingTime	To lock a remote bean instance.
passivationTime	For passivation.

Selecting the task name displays a histogram for the activity on the same, if there is sufficient data available.

Reading Stateless Session Beans

Selecting a stateless session bean name displays the following details:

Table 9: Reading Stateless Session Beans

Task Name	Time taken
transfer:long;long;double;(BusinessMethod)	To execute the applications business method.
transfer:long;long;double;(ActualMethod)	To execute the applications actual method.
preProcessingTime	To complete the tasks that are done prior to processing the actual business methods in the bean.
beanGetTime	To get a bean from the bean pool.
onPoolWaitingTime	To wait for getting a bean from the bean pool.
create:(BusinessMethod)	To execute the applications business method.
postProcesingTime	To complete the tasks that are done after processing the actual business methods in the bean.
creatingTime	To create a bean instance.
riLockingTime	To lock a remote bean instance.

How do I save Diagnostic Data?

To save and store diagnostic data in the local server:

Click Save.
Enter a name for the report to be saved.
Clicking Save displays the following message: ‘The report has been saved by name "<name _moz-userdefined="">"’. The report can be accessed later from the diagnostics home page.
Note: Use Cancel to abort the process.
Click Continue to view other diagnostic data. Click Close on the toolbar to exit Diagnostics.

How do I view Diagnostic Data?

To view diagnostic data:

Locate the saved reports listed under Reports on the Server Diagnostics Reports page.
Select the required report and click Download Report. The file download dialog-box opens.
Select Open this file from current location to view diagnostic data. Select Save this to disk to make a local copy.

How do I delete Diagnostic Data?

To delete diagnostic data from the Server, click Trash on the toolbar. If data is saved as a report, select the reports to be removed and click Delete.

Related Topics:


© Pramati Technologies 2007	Runs on Pramati Server \| Feedback \| Legal

How do I interpret Diagnostics?

Table of Contents

How do I interpret Diagnostics?

How do I read Transaction Diagnostics?

How do I read Datasource Diagnostics?

How do I read Application Diagnostics?

How do I save Diagnostic Data?

How do I view Diagnostic Data?

How do I delete Diagnostic Data?