04 2:15 PM
> To: JBoss List
> Subject: RE: [JBoss-user] Dirty read with commit option B on
> JBoss 3.2.0
>
> Hi, thanx for response.
>
> On you question : No. I use default JBoss preferences for
> entity beans without on-find or on-load strategies.
>
> Actually i have
> [mailto:[EMAIL PROTECTED] On Behalf Of
> > Maxim Mikhelman
> > Sent: Thursday, June 03, 2004 11:08 AM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-user] Dirty read with commit option B on JBoss 3.2.0
> >
> > I use JBoss 3.2.0 with container configuration
user] Dirty read with commit option B on JBoss 3.2.0
>
> I use JBoss 3.2.0 with container configuration "Standard CMP
> 2.x EntityBean" (commit option B, pessimistic locking). All
> code run within transactions, user or container (required).
>
> I see next strange behavi
I use JBoss 3.2.0 with container configuration "Standard CMP 2.x
EntityBean" (commit option B, pessimistic locking). All code run within
transactions, user or container (required).
I see next strange behavior:
1. JBoss starts first transaction that find some Entity Bean instance A,
use it with get
