[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-769) exception in destroy method results in "javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean"
[ http://jira.jboss.com/jira/browse/EJBTHREE-769?page=all ]
Bill Burke closed EJBTHREE-769.
-------------------------------
Resolution: Done
the correct fix was to check to see if the bean was already discarded or removed. If it
was, then don't remove again in StatefulRemoveInterceptor
exception in destroy method results in
"javax.ejb.EJBNoSuchObjectException: Could not find Stateful bean"
---------------------------------------------------------------------------------------------------------
Key: EJBTHREE-769
URL: http://jira.jboss.com/jira/browse/EJBTHREE-769
Project: EJB 3.0
Issue Type: Bug
Reporter: Gavin King
Assigned To: William DeCoste
Fix For: EJB 3.0 RC10 - FD
This affects JBoss 4.0.5.
When a system exception occurs in a @Destroy method of a SFSB, the bean gets removed
(because of the @Destroy annotation), then the container tries to remove it a second time
(because of the exception), and this results in the swallowing of the original exception,
with an EJBNoSuchObjectException taking its place.
Solution: the interceptor that handles the @Destroy annotation should not try to remove
the SFSB when the destroy method throws an exception.
--
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