Monitoring Pramati EJB Server

Transcription

1 Monitoring Pramati EJB Server 17 Overview The EJB Server manages the execution of enterprise applications that run on the J2EE server. The JAR modules deployed on the Server are supported by the EJB container. Monitoring EJB Server Select Monitor > EJB Server in the Explore panel on the Console. The screen appears as below: Monitoring EJB Server In case no application has been deployed, use Configure > Applications > Java Applications to deploy a *.jar. The details provided in the display panel are: Table 1: Monitoring EJB Server details Field Name Transactions Description Displays names of the applications deployed on the EJB Server Displays the number of transactions taking place for the deployed application.

2 168 Pramati Server 3.5 Administration Guide Clicking on the application name displays the following screen: Monitoring setails about applications and transactions on the EJB Server The details provided are divided into two sections: Application specific details Transactions related details Note: These statistics can also be viewed using the Monitor > Applications > Java Applications. The procedure has been described in the chapter Monitoring Applications in Pramati Server. Monitoring EJB applications The details provided for the deployed *.jar are as follows: Table 2: Jar Details Fields Name Bean Type Current Pool Free Pool Ready Pool Used Pool Statistics Description Displays the names of the beans present in the jar file. Displays the type of the bean, whether Stateful, Stateless or Container Managed Persistence. Displays the size of the current pool. Displays the size of the free pool. Displays the size of the pool ready to be used. Displays the used pool size. Clicking this displays the statistics about the selected bean.

3 CHAPTER 17 Monitoring Pramati EJB Server 169 Viewing bean Statistics Clicking Statistics against a bean name displays statistics regarding the same. For example, if in the screen displayed above, Statistics is selected against the CheckingBean bean, the following screen is displayed: Viewing Bean Statistics The following details are displayed: Table 3: Bean Statistics Bean Type Instantiation Count Destroy Count Count Time Details Count Min Time Max Time Avg Time Displays the type of the selected bean, whether Stateful, Stateless or Container Managed Persistence. Displays the number of beans instantiated. Displays the number of beans that were destroyed. Displays the number of exceptions that were encountered. Displays time details related to the beans. These details are not available for the Stateless Session Beans. Refers to the number of times the bean is accessed. Refers to the minimum time taken by the transaction to commit Refers to the maximum time taken by the transaction to commit Refers to the average time required by the transaction

4 170 Pramati Server 3.5 Administration Guide Table 3: Bean Statistics Waiting Thread PK Waiting Thread Pool Details Load Time (ms) Refers to the load time for an Entity bean. Displayed only if the selected bean is an Entity bean. Store Time (ms) Refers to the store time for an Entity bean. Displayed only if the selected bean is an Entity bean. Locking Time (ms) Refers to the locking time for an Entity bean. Displayed only if the selected bean is an Entity bean. Activation Time (ms) Refers to the time taken to activate a bean. Passivation Time (ms) Refers to the time taken to passivate a bean. Alive time (ms) Refers to the alive time for the Stateful Session Bean. Displayed only if the selected bean is a Stateful Session Bean. Displays details related to the waiting threads. Min Refers to the minimum number of threads waiting to acquire lock on the bean. Max Refers to the maximum number of threads waiting to acquire lock on the bean. Avg Refers to the average number of threads waiting to acquire lock on the bean. Min Limit Refers to the minimum number of threads that are allowed to wait for a particular bean. Max Limit Refers to the maximum number of threads that are allowed to wait for a particular bean. Waiting Threads Refers to the current number of waiting threads. Displays details related to the Primary Key waiting threads. Min Refers to the minimum number of threads waiting on the Primary Key. Max Refers to the maximum number of threads waiting on the Primary Key. Avg Refers to the average number of threads waiting on the Primary Key. Displays details related to the pool size. Min Refers to the minimum pool size. Max Refers to the maximum pool size. Avg Refers to the average pool size. Min Limit Refers to the minimum pool size limit set by the user. Max Limit Refers to the maximum pool size limit set by the user. Pool Size Refers to the current pool size. Free Pool Size Displays the size of the free pool.

5 CHAPTER 17 Monitoring Pramati EJB Server 171 Table 3: Bean Statistics In Use Pool Size Active Pool Size Displays the used pool size. Displays the size of the current pool. Viewing Transaction Statistics The following details are displayed for the transactions that have taken place on the deployed application: Viewing Transaction Statistics Table 4: Transaction statistics Total Started Count Min Time Max Time Refers to the total number of transactions that took place Refers to the total number of transactions started Refers to the number of transactions committed Refers to the minimum time taken by the transaction to commit Refers to the maximum time taken by the transaction to commit

6 172 Pramati Server 3.5 Administration Guide Table 4: Transaction statistics Committed Container Managed RollBack Bean Managed RollBack Avg Time CMT BMT CMT BMT Heuristic Mixed Heuristic Rollback Set Rollback Only Total Heuristic Mixed Heuristic Rollback Set Rollback Only Total Refers to the average time required by the transaction Refers to the started Container Managed Transactions. Refers to the started Bean Managed Transactions. Refers to the time taken for a transaction to commit Refers to the committed Container Managed Transactions. Refers to the committed Bean Managed Transactions. Refers to the maximum time taken for Container Managed Rollback was some problem in the network and also that the data got corrupted. was some problem in the network. However, the database/ resource was not affected because of this rollback. Refers that the transaction was not committed because of a constraint or logic that was specified in the code. Refers to the total number of rollbacks in the container managed transactions. Refers to the maximum time taken for Bean Managed Rollback was some problem in the network and also that the data got corrupted. was some problem in the network. However, the database/ resource was not affected because of this rollback. Refers that the transaction was not committed because of a constraint or logic that was specified in the code. Refers to the total number of rollbacks in the bean managed transactions.