aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Session Bean exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Session Bean exception" Watch "Session Bean exception" New topic
Author

Session Bean exception

Ranadhir Nag
Ranch Hand

Joined: Mar 09, 2006
Posts: 138
I believe to have read that RunTimeExceptions raised from session beans do not propagate as-is to client;and cause beans to be removed from the pool and obliterated.
We have a stateless session bean throwing an IllegalArgumentException.
This get wrapped as EJBException at the client which is as expected.
However,we do not see the bean instance being discarded from the pool ( ejbremove is not invoked).

I would have expected the ejbremove to have been invoked for this bean instance.
THe pooling parameters are:
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>50</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
</stateless-session-descriptor>

Any help is appreciated.

 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Session Bean exception