The issue is that the transaction never gets properly cleaned up. This is fixed in the 2.1 code. Sorry that there's no 2.0 patch. James Cook wrote: > > Slightly scarier still... > > if I call setRollbackOnly(); before throwing the EJBException() it still does > not rollback the transaction. > > jim > > ----- Original Message ----- > From: "James Cook" <[EMAIL PROTECTED]> > To: "JBoss-User" <[EMAIL PROTECTED]> > Sent: Thursday, March 08, 2001 11:15 AM > Subject: [jBoss-User] Bug: EJBException does not result in a transaction > rollback > > > In my ejbStore() I am throwing an EJBException and it is not causing a > > transaction rollback. Because the transacation stalls, the container actually > > appears to lock up in these cases. The client also stalls. > > > > If I change the exception to RemoteException, all works as expected. The > > transaction is aborted. According to the spec all non-application exceptions > > should cause an automatic rollback. I believe that EJBException should be > > considered a non-application exception. > > > > jim > > > > > > > > -- > > -------------------------------------------------------------- > > To subscribe: [EMAIL PROTECTED] > > To unsubscribe: [EMAIL PROTECTED] > > > > > > -- > -------------------------------------------------------------- > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED]
