|
Measures reported by WebLogicEjbTest
This test monitors the
state of specific EJB components hosted on a WebLogic server 6.0 or higher
using JMX. Following are three different kinds of EJB components that can be
hosted on a WebLogic server 6.0 or higher:
a. A stateful session
bean is an enterprise bean that acts as a server-side extension of the
client that uses it. The stateful session bean is created by a client and
will work for only that client until the client connection is dropped or the
bean is explicitly removed.
b. A stateless session
bean is an enterprise bean that provides a stateless service to the client
c. An entity bean
represents a business object in a persistent storage mechanism such as a
database. For example, an entity bean could represent a customer, which
might be stored as a row in the customer table of a relational database
eG monitors all the above
components. The measures made by this test are as
follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Tx_commit_rate |
Indicates
the rate at which transactions are committed for a particular bean. |
Trans/Sec
|
Comparing
this value across all the deployed beans can give an idea of the
relative importance of the beans in supporting user accesses. A sudden
change in user access patterns can be indicative of a change in the
user workload. |
| Tx_rollback_rate |
Indicates
the rate at which the transactions are rolled back for a particular
bean. |
Trans/Sec
|
A
high rollback rate indicates a problem with specific beans. Possible
reasons for this could be problems with the design and
implementation of the specific bean or problems with any of the
dependent servers of the bean (e.g., database server) |
| Tx_inflight |
Number
of transactions currently in progress through a particular bean. |
Number
|
A
significantly high value may denote a load on the specific bean. This
may indicate that specific transactions are taking too long to process
requests. |
| Num_waiting_rate |
This
measure corresponds to only stateless session bean. This indicates the
rate at which connections are established by the client with the
instances of the bean. |
Conns/Sec
|
A
high value signifies that it is taking more time for the clients to
access an instance of the bean from the pool. |
| Timeout_rate |
This
measure also corresponds to the stateless session beans. The measure
indicates the rate at which instances are timed out by the bean |
Conns/Sec
|
A
high value indicates a problem with a specific bean. Again, the
problem can be specific to the bean implementation or with any of the
dependent servers of the bean. |
| Idle_bean_pct |
The
percentage of beans those are idle in the cache |
Percent
|
A
high percentage indicates a memory bottleneck. The timeout of the
session beans could be one of the possible reasons.
|
|