: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Scott M Stark
[EMAIL PROTECTED]
Sent: Thursday, May 23, 2002 8:18 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error
messages
PROTECTED]
Sent: Thursday, May 23, 2002 7:45 PM
Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS
RA
He who codes wins the vote. This issue does not bother me enough
to
change
anything.
Regards,
Hiram
From
, 2002 8:18 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error messages
when this does happen... or just leave it as is?
--jason
On Thursday 23 May 2002 08:00 pm, Scott M Stark wrote:
I don't see sufficient
PROTECTED]
To: [EMAIL PROTECTED]; Scott M Stark
[EMAIL PROTECTED]
Sent: Thursday, May 23, 2002 8:18 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error
messages when this does happen... or just leave
PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error
messages when this does happen... or just leave it as is?
--jason
On Thursday 23 May 2002 08:00 pm, Scott M Stark wrote:
I don't
Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
He who codes wins the vote. This issue does not bother me enough
to
change
anything.
Regards,
Hiram
From: David Maplesden [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED
]
Sent: Thursday, May 23, 2002 8:18 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error
messages when this does happen... or just leave it as is?
--jason
On Thursday 23 May 2002
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error
messages when this does happen... or just leave it as is?
--jason
On Thursday 23 May 2002 08:00 pm, Scott M Stark wrote:
I
Nothing like a cry for help to get me interested.
From a brief look at the source and from what I can remember from my work on
this stuff the problem is in JBossMQ SpySession class. From what I can see
the sendMessage method needs to be synchronized and I think that will solve
your problem.
Nothing like a cry for help to get me interested.
=)
So you either need to patch SpySession sendMessage so that it is
synchronized or patch the client code (the code calling the JBossMQ stuff)
so that it doesn't have threads calling commit on the session at the same
time other threads are
: Thursday, May 23, 2002 8:31 AM
To: [EMAIL PROTECTED]; David Maplesden;
'[EMAIL PROTECTED]'
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Nothing like a cry for help to get me interested.
=)
So you either need to patch SpySession sendMessage so
: Thursday, May 23, 2002 8:31 AM
To: [EMAIL PROTECTED]; David Maplesden;
'[EMAIL PROTECTED]'
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Nothing like a cry for help to get me interested.
=)
So you either need to patch SpySession sendMessage so
So, this does indeed get interesting... my client code is calling a SFSB
which
has a JMS RA, which has the SpySession.
I do have a timer thread sending back periodic stats with the same SFSB
(my
bad) which the main thread uses... but shouldn't the SFSB detect this and
throw an exception
From: Jason Dillon [EMAIL PROTECTED]
...
And is there any reason why SpySession.sendMessage() should NOT be
synchronized?
If anything SpySession.sendMessage() should try to detect the concurrent
access from 2 threads and throw an exception stating that the JMS spec is
being violated by the
Yes it should. We have a testcase for this, but how is the timer
interacting with the SFSB, through its remote/local interface?
I have a wrapper object that connects to the SFSB (home.create()) which the
main thread uses to send JMS messages, which a timer also uses to send back
periodic
Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Scott M Stark
[EMAIL PROTECTED]
Sent: Thursday, May 23, 2002 6:49 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
the session check conncurent access better to let
beginer user know when he has potentialy made a semantical error.
Regards,
Hiram
From: David Maplesden [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]'
[EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Seeing occasional Invalid tx
: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Date: Fri, 24 May 2002 13:36:43 +1200
I hate to disagree with Scott and Hiram but I feel that just
because the
spec says Sessions should only be used in 1 thread does not
neccessarily
mean that we should restrict their usage
On Thursday 23 May 2002 07:24 pm, Scott M Stark wrote:
The last thing to clarify is are your JMS transactions spanning
multiple SFSB method calls? If they are you can be violating
the single-thread use of the session without multiple threads
being active in the SFSB because you could be
, May 23, 2002 7:45 PM
Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
He who codes wins the vote. This issue does not bother me enough to
change
anything.
Regards,
Hiram
From: David Maplesden [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: '[EMAIL PROTECTED
it.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 23, 2002 7:45 PM
Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
He
PROTECTED]
To: [EMAIL PROTECTED]; Scott M Stark
[EMAIL PROTECTED]
Sent: Thursday, May 23, 2002 8:18 PM
Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
Does this mean we should not try to produce more meaningful error messages
when this does happen... or just leave
22 matches
Mail list logo
