FYI,
There definately is a race condition. I modified InstanceSynchronization
and put a sleep after ctx.setTransction(null) and had 2 threads accessing
the same bean. When thread 1 rolled back and slept after the
setTransaction(null), thread 2 wokeup.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bill
> Burke
> Sent: Thursday, June 07, 2001 11:42 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] race condition between
> EntityInstanceInterceptor and InstanceSynchronization?
>
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of danch
> > (Dan Christopherson)
> > Sent: Thursday, June 07, 2001 11:00 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] race condition between
> > EntityInstanceInterceptor and InstanceSynchronization?
> >
> >
> > Bill Burke wrote:
> >
> > > Another possible bug related to this same problem. [please
> read below].
> > >
> > > EntityInstanceInterceptor gets the mutex of the Entity's key
> > before going
> > > into the do..while loop. If a different thread/transaction
> > rollsback, the
> > > mutex gets detached from the EntityEnterpriseContext and the
> > thread in the
> > > do..while loop is acquiring a lock on a context that is not
> > attached. Am I
> > > missing something here?
> >
> >
> > I don't think so. Do we need to mark the mutex as invalid? When we add
> > teh wait/notify, invalidation should also notify.
> >
> >
> > >
> > > I'd really like to go in and fix this problem, but I really
> > need another set
> > > of eyeballs to make sure I'm doing things right. Danch, can
> > you volunteer
> > > to help? Also, while I'm in this code, maybe I should consider
> > adding the
> > > "Missing wait/notify" and remove that buggy do..while loop as well.
> > >
> >
> > I can certainly review. I won't have much time for investigation until
> > this evening, and then my wife may have other plans for my time.
> >
>
> Thanks. My wife has veto power as well :-) ....It may take me awhile to
> come up with a solution anyways.
>
> Bill
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
