eG Monitoring
 

Measures reported by GfEjbSFSBeanTest

The stateful container manages the stateful session beans, which, by definition, carry the client-specific state. There is a one-to-one relationship between the client and the stateful session beans. At creation, each stateful session bean (SFSB) is given a unique session ID that is used to access the session bean so that an instance of a stateful session bean is accessed by a single client only. Stateful session beans are managed using cache.

This test monitors the stateful container and reports the number and nature of methods that were invoked on the container. In the process, the test reports the status of the stateful session beans - whether they have just been created, are in the ‘ready’ state, are in the ‘passivate’ state, or have been removed from the container.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Method_create_count Indicates the number of times the create method was invoked on this container. Number  
Method_ready_count Indicates the number of times in the last measurement period the ‘Ready’ method was invoked on this container. Number A bean in the cache represents the ready state in the EJB lifecycle. This means that the bean has an identity (for example, a primary key or session ID) associated with it.
Passive_count Indicates the number of beans in this container that were in the passivated state during the last measurement period. Number Beans moving out of the cache have to be passivated or destroyed according to the EJB lifecycle. Once passivated, a bean has to be activated to come back into the cache. Typically, bean passivation occurs when the max-cache-size setting is exceeded and the cache overflows. A bean is also passivated if it outlives the cache-idle-timeout-in-seconds settings.
Remove_count Indicates the number of times the ‘remote’ method was invoked on the beans in this container during the last measurement period. Number If a stateful session bean remains idle in the backup store for a duration beyond the configured removal-timeout-in-seconds, then it is removed from the backup store and will not be accessible to the client. The default value is 60 minutes.