[ http://jira.jboss.com/jira/browse/JBAS-1599?page=history ]

Darran updated JBAS-1599:
-------------------------

    Attachment: AbstractInstancePool-patch.txt
                StatelessSessionEnterpriseContext-patch.txt

Attached are two patches for this issue.

'AbstractInstancePool-patch.txt' - This contains the required changes to return 
the permit if creation of a new bean instance fails.

While investigating this problem I saw that if a CreateException is thrown by 
the bean the CreateException is thrown directly back to the client which 
results in the client catching a 'java.rmi.UnexpectedException' the file 
'StatelessSessionEnterpriseContext-patch.txt' contains changes that wrap any 
checked exceptions with an EJBException as well as the runtime exceptions that 
were already wrapped.  The result of this is that if the bean throws a 
CreateException or a RuntimeException the client will allways see a 
ServerException.  We already know that the bean can only throw valid checked 
exceptions as this will have been validated on deployment.

> EJB Pools Strict Maximum Pool Permits Leak
> ------------------------------------------
>
>          Key: JBAS-1599
>          URL: http://jira.jboss.com/jira/browse/JBAS-1599
>      Project: JBoss Application Server
>         Type: Bug
>   Components: EJBs
>     Versions: JBossAS-4.0.2 Final,  JBossAS-4.0.2RC1
>  Environment: All
>     Reporter: Darran
>  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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to