I have finally downloaded and tested this patch with SwiftMQ, and it does indeed
fix the problem. Does anyone object if I go forward with this patch? (Note - I
simplified it a bit, and added some (too much?) commenting).
-Larry
I think I may have tracked down the SwiftMQ bug... let me know
: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
XAResources
I have finally downloaded and tested this patch with SwiftMQ, and it
does
indeed
fix the problem. Does anyone object if I go forward with this patch?
(Note - I
simplified it a bit, and added some (too much?) commenting
David Jencks wrote:
Thanks!!
I want to get this in our testsuite as soon as possible. I'm not sure how
best to do this. Right now the only xa thingy we ship with is the jmxra
adapter.
Just to make sure that we are talking about same testing approach:
XATest has a test case for all
- Original Message -
From: Ole Husgaard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 08, 2002 10:53 AM
Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on closed XAResources
Larry Sandereson wrote:
+1 for changing JBoss TM to allow end(success
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all calls
to isSameRM(). This should cause all connections being enlisted to be given
a unique xid (with different branch qualifiers). I think
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all calls
to isSameRM(). This should cause all connections being enlisted to be given
a unique xid (with different branch qualifiers). I think
Hi,
Scott M Stark wrote:
Why do we have to work around driver bugs at the transaction manager
level? Why not write the TM the way we want and start introducing driver
specific JCA wrappers to deal with these issues?
Makes sense to me.
Then, we wouldn't have to add extra code in the TM code
-Bugs-590816 ] XAProto Errors on
closed
XAResources
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all
calls
to isSameRM(). This should cause all connections being enlisted to be
given
: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
XAResources
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all
calls
to isSameRM(). This should cause all connections
the issues before it even gets to an adapter.
--jason
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-
[EMAIL PROTECTED]] On Behalf Of Ole Husgaard
Sent: Thursday, August 08, 2002 2:10 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
, August 08, 2002 2:03 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
XAResources
I think I may have tracked down the SwiftMQ bug... let me know if
this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false
We already have one of these for InformixXA that I can donate.
-Larry
Could some of these problems be solved by using a custom driver layer
which would resolve these issues at the JDBC layer? Dain was talking
about doing something like this at the last SF training. Then we would
have one
: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
XAResources
Hi,
Scott M Stark wrote:
Why do we have to work around driver bugs at the transaction manager
level? Why not write the TM the way we want and start introducing
driver
specific JCA wrappers to deal
2:45 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on
closed
XAResources
Jason Dillon wrote:
Could some of these problems be solved by using a custom driver
layer
which would resolve these issues at the JDBC layer? Dain was
talking
about doing
Larry Sandereson wrote:
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
This is great. And it sounds right to me.
SwiftMQ doesn't support start(suspend), so they return false for all calls
to isSameRM(). This should cause all connections being enlisted
SwiftMQ doesn't support start(suspend), so they return false for all
calls
to isSameRM(). This should cause all connections being enlisted to be
given
a unique xid (with different branch qualifiers). I think this is
compliant
with the JTA and XA specs.
start(suspend) doesn't make
16 matches
Mail list logo
