| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Error MQJMS2014 - Reason 2012 when using XA API |
« View previous topic :: View next topic » |
| Author |
Message
|
| araghav |
 Posted: Fri May 24, 2002 7:51 am Post subject: JMS Error MQJMS2014 - Reason 2012 when using XA API |
 |
|
Novice
Joined: 21 May 2002
Posts: 12
|
I am getting JMSException (see description below) when trying to call MQXAQueueConnectionFactory.createXAQueueConnection().
I am running program on VAJ (3.5), with JMS in client transport mode.
I have defined all required jar files and tested code without XA APIs.
Exception text:
javax.jms.JMSException: MQJMS2014: Queue manager rejected XA client connection
linked exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2012
-Ashish |
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Fri May 24, 2002 10:26 am Post subject: Re: JMS Error MQJMS2014 - Reason 2012 when using XA API |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| araghav wrote: |
I am running program on VAJ (3.5), with JMS in client transport mode.
|
Ashish,
XA transactions are only supported in bindings mode, not with an MQ client connection.
| Quote: |
2012 X'7DC' MQRC_ENVIRONMENT_ERROR
| Call not valid in environment.
| The call is not valid for the current environment.
| - On Digital OpenVMS, OS/2 Warp, Tandem NSK, UNIX platforms, and Windows NT, one
| of the following applies:
| -- The application is linked to the wrong libraries (threaded or nonthreaded).
| -- An MQBEGIN, MQCMIT, or MQBACK call was issued, but an external unit-of-work
| manager is in use or the queue manager does not support units of work.
| -- The MQBEGIN call was issued in an MQ client environment.
|
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| araghav |
| Posted: Fri May 24, 2002 10:57 am Post subject: But JMS |
|
|
Novice
Joined: 21 May 2002
Posts: 12
|
Stefan,
Thanks for confirming my doubts.
This is true for MQ Java APIs but not completely true for JMS. When I tried with JMS API, transaction worked partly. What I mean by partly is - I can use begin() and end() methods to ensure single phase (or local) transaction (Which is not true for MQ Java) but could not participate in 2 phase transaction.
This will give me some headache as my VAJ (development machine) does not have MQSeries server ( so I can not test my code), where as testing and production m/c will have App Server and MQSeries on same box.
Ashish |
|
| 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
|
|
|
|
