|case. Or maybe we need 2 maps here...???
David,
KISS
marcf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
; > Cc: Jboss-Dev
> > Subject: Re: [JBoss-dev] Bug?: no rollback on tx timeout
> >
> >
> > OK, now I'm confused. Looking at (some of) the code I would think
> that:
> >
> > 1. If nothing is hanging, just taking a really long time, when it all
> gets
>
On 2002.02.21 17:36:46 -0500 Dain Sundstrom wrote:
> > I'm no threading expert, but I can't find any way of communicating with
>
>
> > the hung thread to force it to return.
>
>
> thread.interrupt() works in most cases. It causes the thread to throw
> an InterruptedException.
I think this i
I don't think that works. All it does I think is set a boolean flag
internally.
> -Original Message-
> From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 21, 2002 5:37 PM
> To: David Jencks
> Cc: Bill Burke; Jboss-Dev
> Subject: Re: [JBoss
Hey, thanks for replyingComments are in-lined.
> -Original Message-
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 21, 2002 5:25 PM
> To: Bill Burke
> Cc: Jboss-Dev
> Subject: Re: [JBoss-dev] Bug?: no rollback on tx timeout
>
>
> I'm no threading expert, but I can't find any way of communicating with
> the hung thread to force it to return.
thread.interrupt() works in most cases. It causes the thread to throw
an InterruptedException.
-dain
___
Jboss-development mailin
OK, now I'm confused. Looking at (some of) the code I would think that:
1. If nothing is hanging, just taking a really long time, when it all gets
done the tx will be rolled back just fine, and all resources released.
2. If the db call is hanging, the tx will be marked for rollback, but since
t
Thanks,
Bill
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Christian Riege
> Sent: Thursday, February 21, 2002 4:10 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 21:56, Bill Burke wrote:
> 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.
you're correct. the thrown exception is not a NPE but instead an
IllegalStateExeption; we t
y, 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,
> >
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,
> bewareI'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
All,
I've voiced this concern in the past. When a transaction times out, why
does the method TxCapsule.timedOut only set the status of the transaction as
STATUS_MARKED_ROLLBACK? Why doesn't it actually do a rollback?
A very serious side effect is this scenario:
Something hangs indefinately wi
12 matches
Mail list logo
