[
http://jira.jboss.com/jira/browse/JBAS-1599?page=comments#action_12416413 ]
Bart Vanhaute commented on JBAS-1599:
-------------------------------------
Is this issue also solved for MDBs?
I am running JBAS 4.2.2.GA, and I see
Unexpected error delivering message SpyTextMessage
...
javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000
at org.jboss.ejb3.StrictMaxPool.get(StrictMaxPool.java:122)
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
at $Proxy128.onMessage(Unknown Source)
at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
at org.jboss.mq.SpySession.run(SpySession.java:323)
at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
EJB Pools Strict Maximum Pool Permits Leak
------------------------------------------
Key: JBAS-1599
URL:
http://jira.jboss.com/jira/browse/JBAS-1599
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.2RC1
Environment: All
Reporter: Darran
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.2 Final
Attachments: AbstractInstancePool-patch.txt,
StatelessSessionEnterpriseContext-patch.txt, StrictMaximumTest.zip
When the EJB pools are configured with 'strictMaximumSize' set to true, if an
Exception is thrown from the ejbCreate method of the bean being created to service the
request the permit is not returned before the Exception is thrown to the calling client.
If this keeps happening till all permits are exhausted the clients will start to get the
error: -
'Failed to acquire the pool semaphore' thrown as an EJBException from the get
method of the AbstractInstancePool.
--
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