We use a bean with StrictMaxPool and maxSize=1.
The method of this bean should not be executed by two threads at the same time.
(Sort of mutual exclusion mechanism.)
Though, when the system is under heavy load, we end up with several instances of the bean.
In the log we see also lots of "javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=3000".
At some point, the jmx-console shows the bean has a MaxSize of 1 and AvailableCount of 308!?
Later, we also activated the TRACE log on org.jboss.ejb3.pool:
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
We got an issue likely related to this one.
We use a bean with StrictMaxPool and maxSize=1.
The method of this bean should not be executed by two threads at the same time.
(Sort of mutual exclusion mechanism.)
Though, when the system is under heavy load, we end up with several instances of the bean.
In the log we see also lots of "javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=3000".
At some point, the jmx-console shows the bean has a MaxSize of 1 and AvailableCount of 308!?
Later, we also activated the TRACE log on org.jboss.ejb3.pool: