| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| exception: client connection not XA enabled |
« View previous topic :: View next topic » |
| Author |
Message
|
| deepu4u |
 Posted: Tue Dec 11, 2007 10:31 pm Post subject: exception: client connection not XA enabled |
 |
|
Apprentice
Joined: 20 Jun 2005
Posts: 37
|
Hi all,
I have this code:
mqProperties.put(MQC.CHANNEL_PROPERTY, channel);
mqProperties.put(MQC.HOST_NAME_PROPERTY, hostname);
mqProperties.put(MQC.PORT_PROPERTY, new Integer(port));
mqProperties.put(MQC.USER_ID_PROPERTY, userID);
mqProperties.put(MQC.PASSWORD_PROPERTY, password);
mqProperties.put("Group", new Object());
mqProperties.put("XAReq", new Boolean(true));
mqProperties.put("Thread affinity", new Boolean(true));
mqProperties.put("SPI", "SPI_ENABLE");
mqProperties.put("Use QM CCSID", new Boolean(true));
fQMGR = new MQQueueManager(qmgr, mqProperties);
MQXAQueueManager xMgr = new MQXAQueueManager(fQMGR);
debug("connected to MQSeries successfully.\n");
debug(" QM : "+fQMGR.name);
xMgr.getXAResource();
but it gives me the following exception:
javax.transaction.xa.XAException: client connection not XA enabled
debug :Unknown exception in connect. ex=client connection not XA enabled
at com.ibm.mq.MQXAResource.createXAException(MQXAResource.java:794)
at com.ibm.mq.MQSESSIONClient.XAOPEN(MQSESSIONClient.java:458)
at com.ibm.mq.MQXAResource.<init>(MQXAResource.java:110)
at com.ibm.mq.MQXAQueueManager.getXAResource(MQXAQueueManager.java:270)
at MQUtility.connect(MQUtility.java:91)
at MQUtility.main(MQUtility.java:690)
Any pointer would be of great help.
thanks,
deepak |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Dec 12, 2007 12:06 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| You can't use XA transactions with the standard MQ client. |
|
| Back to top |
|
|
| atheek |
| Posted: Wed Dec 12, 2007 1:19 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
You need to use extended transactional client (etc) for doing xa transactions over a client link. This is true, even if you have the Queue manager running on the same physical machine as your application. Use bindings mode if you have qmanager on same box for xa to work.
Note that etc is not free unlike non - transactional client; it costs as much as the server. And will be available as a jar file com.ibm.mqetclient.jar which you need to set in the classpath
-Atheek |
|
| 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
|
|
|
|
