Jboss monitoring with warnings on Stateless beans

Jboss monitoring with warnings on Stateless beans

i just have startet an evaluation of the AppManager on our Jboss4.04GA

we use only StatelessSessionBeans on the jboss and get the warning in the appManager

Zustand ist Kritisch.
Ursache:
1. ScrollServerCtrl Erzeugte Instanzen 2010 > 2000 (Schwellwert).
2. TransportServerCtrl Erzeugte Instanzen 2034 > 2000 (Schwellwert).

... but if a have a look on the server i can see the following :
TransportServerC... Stateless Session Bean FERPSEJB.jar 3.140 0 2 NA NA


... this means that only 2 beans are availabe ...
Question 1: why does the system create a warning on too many StatelessSessionBeans instances ... the user cannot control the amount of stateless instances

Question2: is the number of instances wrong ... mybe this is only the number of bean-create statements ... in EJB a create() on a statelessbean does not create a new instance if one is on the server available !















                New to ADSelfService Plus?