JEUS Stateful Session Bean Test

A stateful session bean is a type of enterprise bean, which preserve the conversational state with client. A stateful session bean as per its name keeps associated client state in its instance variables. EJB Container creates a separate stateful session bean to process client's each request. As soon as request scope is over, statelful session bean is destroyed.

This test monitors the stateful container and reports the number and nature of methods that were invoked on each 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. Additionally, this test also reveals insights on the EJB beans and EJB objects in each statefull container.

Target of the test : A JEUS Web Application server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each stateful session bean container configured on the target server being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port at which the specified host listens. By default, this is 9736.
Username and Password	To enable the eG agent to communicate and continuously monitor the target JEUS server, the eG agent should be configured with the credentials of the admin user on the server. In highly-secure environments, administrators may not want to expose the credentials of the user possessing administrator privileges. In such environments, for monitoring the JEUS application server, administrators have an option to create a new user on the JEUS server and assign administrator privilege to that user. The steps to create a new user with administrator privilege are explained in Creating a User with Administrator Privileges topic. This user should also be granted permission to access the JNDI objects on the server such that the eG agent can pull out performance metrics from the target server. To know how to grant permission to access the resources, refer to Granting the Administrator Role access to JNDI Binding Objects topic.
Confirm Password	Confirm the Password by retyping it here.
Listener Port	To collect metrics from the target server, the eG agent should be configured to use JMX to connect to the JRE used by the target server and pull out the performance metrics. By default, JMX support is enabled for the JRE used by the target server. The JMX connector listens on port 9736, by default. Therefore, type 9736 as the Listener Port. However, if the host is configured with multiple sever instances, then you should specify the port number at which the JMX listens in your environment. Ensure that you specify the same port that you configured while creating the listener (if required) using the JEUS WebAdmin Console. To know the details on the listener port, refer to Enabling JMX Support for the JEUS Web Application Server topic.
Export name	The export name is the reference name of the RMI connector that is to be used as a JMX connector. The procedure to obtain the export name is detailed in Enabling JMX Support for the JEUS Web Application Server topic. Specify the name of the export against this parameter.
Server name	Specify the name of the target sever for which the JVM monitoring is enabled. To obtain the name of the server, refer to Enabling JMX Support for the JEUS Web Application Server topic.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Create method calls	Indicates the number of times the create method was called on this container during the last measurement period.	Number
Ready method calls	Indicates the number of times the remedy method was called on this container during the last measurement period.	Number	Greater the value of this measure, better will be the application performance.
Remove method calls	Indicates the number of number of times the remove method was invoked on this container during the last measurement period.	Number
Passive method calls	Indicates the number of number of times the passive method was invoked on this container during the last measurement period.	Number	The container invokes the Passivate method within the bean to provide the bean with a chance to clean up its resources, such as sockets held, database connections, and hash tables with static information. All these resources can be reallocated and re-created during the ejbActivate method.
Active ejb objects	Indicates the number of ejb objects that are currently active in this container.	Number
Remove ejb objects	Indicates the number of ejb objects that were removed from this container during the last measurement period.	Number
Total ejb objects	Indicates the total number of ejb objects in this container.	Number
Active ejb beans	Indicates the number of ejb beans that are currently available for processing the client requests.	Number	A high value is desired for this measure. A low value indicates that adequate beans are not available to service the client requests.
Total ejb beans	Indicates the total count of the ejb beans on this container during the last measurement period.	Number