Hi, To follow up one of my posts regarding "TransactionRollbackLocalException caused stateful session gone?", I have a question which in need of the experts to shed some lights.
Basically the problem is when a callee (a stateless session bean) thrown a runtime exception, it caused the caller bean (container-managed stateful session bean)'s instance gone. Each time when I re-submit the request after the exception thrown, the app server always says that the activation of the stateful bean fails with a file not found for the session bean. [I'm using JBoss 4.0] I understand EJB spec states that bean should be removed from the container if runtime exception occurs. In this case, TransactionRolledbackLocalException is runtime exception so, stateless session bean should be removed after this exception. However, why caller bean (stateful session) also gone? For those who's using JBoss 4.0, any idea? How do I save the stateful session bean from being thrown away in case of callee thrown runtime exception? Regards, Karen =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
