StrictMaxPool for SFSB does not decrease Pool-Usage on bean-removal ------------------------------------------------------------------- Key: EJBTHREE-1358 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1358 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.1.GA Environment: Java 1.5.0_11 @Stateful(name="Lektorat") @PoolClass(value=org.jboss.ejb3.StrictMaxPool.class, maxSize=1000, timeout=10000) @Cache(org.jboss.ejb3.cache.NoPassivationCache.class) public class LektoratImpl implements Lektorat { .... Reporter: Stephan Pelikan Priority: Minor When using SFSB in the old fasioned way for long life operations - not as substitution for SLSB for accessing an extended EntityManager within a short-life-period (http-request) - we mentioned several side-effects (not covered in this JIRA-entry) which we could be trace back to the default-poolclass "ThreadLocalPool". So we decided to use instead the "StrictMaxPool"-class. Now - and this is the bug we found - we could see that the StrictMaxPool's semaphore is not decreased on SFSB-removal which leads to errors upon 1000 (our limit) SFSB has been created. We have mentioned that SFSB's removal does not call the pool's method "release" (The bean should not be reused) but the method "remove" isn't overwritten by StrictMaxPool so the semaphore is never decreased. -- 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