| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| dspmqtrn question |
« View previous topic :: View next topic » |
| Author |
Message
|
| guest468 |
 Posted: Tue Nov 24, 2009 1:16 pm Post subject: dspmqtrn question |
 |
|
Centurion
Joined: 30 May 2006
Posts: 146
Location: NY
|
HiGuys,
I have a question regarding dspmqtrn.
We have one qmgr supporting a couple of applications. Most of them use d/b. The MQ is not configured for XA. And the apps are running in WAS and they specify XA enable in queue def'n. Now the QMGR is running in a different dedicated server and all the apps connect there using SVRCONN. As you can see this makes it ineligible for XA. But when I check dspmqtrn -e, i see indboubt transactions once in a while for a short while. Not sure if they are real XA or just locally coordinated txns erroneously showing up there?
Thanks,
Dave |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Nov 24, 2009 1:35 pm Post subject: Re: dspmqtrn question |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| guest468 wrote: |
| As you can see this makes it ineligible for XA. |
Not if the extended client is in use, which IIRC ships with WAS. Or the jar for it is with WAS. Or something.
But no, using client connections doesn't preclude the use of XA it just makes it slightly more involved. And possibly more expensive (in license terms)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| guest468 |
| Posted: Tue Nov 24, 2009 2:29 pm Post subject: |
|
|
Centurion
Joined: 30 May 2006
Posts: 146
Location: NY
|
Thanks Vitor.
that explains everything. I will check with concerned developers on this. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Nov 25, 2009 7:01 am Post subject: Re: dspmqtrn question |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| guest468 wrote: |
| when I check dspmqtrn -e, i see indboubt transactions once in a while for a short while. Not sure if they are real XA or just locally coordinated txns erroneously showing up there? |
All is well. These transactions are only in a state eligible to be reported by dspmqtrn for a short while. This short while is the gap in time betwen the 2 phases of a 2-phase commit protocol.
If (NB. this is not the case you have described) you had a transaction that was being outputted by dspmqtrn repeatedly, then this would suggest the transaction had got stuck in the "indoubt" state that exists between the 1st and 2nd phases of 2 phase commit. A possible reason for this to happen is that contact was broken between MQ and the application server at that point in time. There are steps you can take to recover that type of situation and they would begin with a restart of the application server (at which time it will contact MQ to ask MQ about any indoubt transactions it knows about). There are also other tools for use in an emergency that will force the commit or rollback of such a transaction.
But having said all of that, the observations you reported sound like business as usual, no problems!  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
