I thought a bean wasn't allowed to be passivated if it was involved with a transaction?
Check out the canPassivate method on the instance cache. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Christian Riege > Sent: Thursday, February 21, 2002 3:26 PM > To: Bill Burke > Cc: JBoss Dev list > Subject: Re: [JBoss-dev] Bug?: no rollback on tx timeout > > > hi, > > On Thu, 2002-02-21 at 20:47, Bill Burke wrote: > > P.S. I need to solve this problem for work. So if I get no feedback, > > beware....I'll be making changes. > > There's one more issue which might be related to this (or not at all, I > don't have the necessary insights): > > When a Bean is enrolled in a transaction and the bean gets passivated > (either because the transaction is taking too long or your bean cache is > running low), the server will throw a lot of NPE's and the transaction > will be marked for rollback -- even if the DB stuff would actually > commit at the end of the transaction. > > Regards, > Christian > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
