I have a Web Application deployed on glassfish 3.1 (build 43) I am using
Stateless Singelton SessionBeans and it is critical to have exactly single
instance of this bean for Thread safety issues. I got some concurrency
problem so I enabled monitoring for EJB Container, and I notices that
glassfish is creating more than single instance for that Session Bean
(NumBeansInPool is 2 or more) Does anyone have an explanation for that?
Regards, Hazem
--
[Message sent by forum member 'hazem']
View Post: http://forums.java.net/node/885040