From: Bill Burke [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 10:45 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
RequiresNew should always work. Remember, standardjboss.xml has changed so
you can't re-use old configurations between
September 20, 2001 7:27 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
> You mentioned to get the latest form Branch_2_4.
> Does this mean the 2.4.1 doesn't support concurrent access for
> RequiresNew?
>
> T
JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
at least a changelog would help.
Probably the default xml file as well
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
|Burke
|Sent: Wednesday, September 19, 2001 2:16 PM
|To: [EMAIL PROT
n be improved later.
|
|Regards,
|
|Bill
|
|> -Original Message-
|> From: [EMAIL PROTECTED]
|> [mailto:[EMAIL PROTECTED]]On Behalf Of James
|> Cook
|> Sent: Wednesday, September 19, 2001 1:31 PM
|> To: [EMAIL PROTECTED]
|> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2
I want to see a simple repro case
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Todd
|Huss
|Sent: Tuesday, September 18, 2001 8:16 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
|
|
|I just upgraded
uson, Doug
> Sent: Wednesday, September 19, 2001 9:55 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
> Does this mean that if you leave all the interceptor then there
> is no transactional locking on the bean?
>
&
: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
Todd,
I cannot reproduce this problem. You're going to have to give me a test
case before I believe you. Also, do you use standardjboss.xml to create
your Entity Bean configuration? Or d
ge-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of James
> Cook
> Sent: Wednesday, September 19, 2001 1:31 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
> Bill,
>
> Since there is little documen
Bill,
Since there is little documentation regarding locking, can you clear up a
question?
Don't take this as a slam. All of the major commercial vendors have
discovered that it is problematic to perform serialization of client access
to EJB's in the container. [We can expound upon this, if you f
0
> > 600
> > 400
> >
>60
> >
>1
> > 0.75
> >
> >
>
0
> > 600
> > 400
> >
>60
> >
>1
> > 0.75
> >
> >
>
r 19, 2001 9:47 AM
Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
> Thanks Bill, your PLEASE NOTE was indeed my problem. During the upgrade I
> didn't replace my standardjboss.xml so the Lock interceptor was
> missing which was affecting my BMP entity beans.
>
&
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Todd
> Huss
> Sent: Wednesday, September 19, 2001 12:48 PM
> To: [EMAIL PROTECTED]
> Cc: Bill Burke
> Subject: RE: [JBoss-dev] RequiresNew Locking Bug in JBoss 2.4.1
>
>
&
0.75
>
>
>
> 100
> 10
>
> A
>
>
>
>
> > -Original Message-
10
A
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Todd
> Huss
> Sent: Tuesday, September 18, 2001 8:16 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] RequiresNew Locking Bug in JBoss 2
Can you give a simple test case? I'll look into this.
Bill
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Todd
> Huss
> Sent: Tuesday, September 18, 2001 8:16 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] Requir
Report bugs at sourceforge:
http://sourceforge.net/tracker/?group_id=22866&atid=376685
- Original Message -
From: "Todd Huss" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 18, 2001 5:16 PM
Subject: [JBoss-dev] RequiresNew Locking Bug
I just upgraded from JBoss 2.4.0 to JBoss 2.4.1 and noticed some of the
locking code has changed. I have an entity bean with all methods having
the transaction attribute set to "RequiresNew" and works great under JBoss
2.4.0. As soon as I upgraded to 2.4.1 though, I started getting race
condition
18 matches
Mail list logo
