Posted: Thu Oct 21, 2010 3:18 am Post subject: XAResource.start blocking
Newbie
Joined: 20 May 2009 Posts: 9
Hi there.
I have an application using the WMQ JCA Adapter. It is:
1. Receiving messages from queue "A" through the JCA inflow.
2. Connecting and sending to another message to queue "B".
All works fine when using the regular (non XA) connection factory, but when using the XA connection factory, enlisting the XAResource from the XA Session in the active transaction results in a thread block (see stack below) in the XAResource.start.
I'm testing on WMQ 7 (with the 7.0.1.3 patch). I think () I've also disabled connection sharing for the channel. I say "think" because I'm not totally sure which config setting does this - I changed the Default Bind Type (on the "Extended" config on the queue manager properties) from shared to isolated. Have a feeling this is not the correct setting
Just wondering if anyone has seen this before and if there was a solution for it. I'm sure it's something stupid I'm doing.
Code:
Name: WorkManager(2)-3
State: WAITING on com.ibm.mq.jmqi.remote.internal.RemoteHconn$AsyncTshLock@19fa786
Total blocked: 0 Total waited: 42
OK... sorry... I think I found the trick with the channels and setting the sharing... I created a Server Connection Channel in the Advanced settings on the Queue Manager, set the "Sharing Conversations" setting (in Extended config) to 1. I then set the new channel as the channel on my XA connection factory.
Same result however... JmqiXAResource.start thread blocks.
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