If SingletonStatelessSessionInstancePool is used for a SLSB, container MBean state is reported incorrectly ---------------------------------------------------------------------------------------------------------- Key: JBAS-5528 URL: http://jira.jboss.com/jira/browse/JBAS-5528 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA Environment: JDK 1.4.2, Windows NT 5.1, Cygwin (any other anvironment should do as well, though). Reporter: Andrew Shcheglov Assigned To: Alexey Loubyansky If SingletonStatelessSessionInstancePool instead of regular StatelessSessionInstancePool is used for a SLSB, State/StateString JMX attributes of the container MBean (jboss.j2ee:jndiName=XXX,plugin=pool,service=EJB) are always 8/Registered. This is most probably caused by the fact that org.jboss.ejb.plugins.SingletonStatelessSessionInstancePool class directly overrides create()/start()/stop()/destroy() operations with empty implementations, which any MBean derived from ServiceMBeanSupport shouldn't. This seems even more useless since AbstractInstancePool (the direct superclass of SingletonStatelessSessionInstancePool ) doesn't override any methods from ServiceMBeanSupport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira