ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » JMSException: MQJMS2007

Post new topic  Reply to topic
 JMSException: MQJMS2007 « View previous topic :: View next topic » 
Author Message
vedantpatil
PostPosted: Wed Jul 13, 2005 4:19 am    Post subject: JMSException: MQJMS2007 Reply with quote

Novice

Joined: 10 Mar 2005
Posts: 19

I got the following exception when using JMS API to write a message in an XA context.

javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironm
ent.java:530)
at com.ibm.mq.jms.MQQueueSender.sendInternal(MQQueueSender.java:791)
at com.ibm.mq.jms.MQQueueSender.send(MQQueueSender.java:225)
at com.ibm.mq.jms.MQQueueSender.send(MQQueueSender.java:258)
at

Can anyone please suggest what does this error code indicate.

Thanks.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jul 13, 2005 4:58 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Capture the linked exception.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
vedantpatil
PostPosted: Wed Jul 13, 2005 10:27 pm    Post subject: MQJMS2007 Reply with quote

Novice

Joined: 10 Mar 2005
Posts: 19

Th Linked exception is as below

com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2072

We are using an MDB deployed in weblgic 8.1 to write messages to MQ 5.3 Queue uisng an XA connection.

If we use the same setup with normal connection, it works fine.
Please find below the snippet of code used.

//Lookup for the XA QCF
XAQueueConnectionFactory factory = (XAQueueConnectionFactory)l_context.lookup (l_qcf);

// Create a QueueConnection, QueueSession
connection = factory.createXAQueueConnection ();
session = connection.createXAQueueSession ();

Queue ioQueue = (Queue)l_context.lookup (l_queue_name);
l_context.close ();
connection.start ();

QueueSender queueSender = (session.getQueueSession ()).createSender (ioQueue);


Is it that we are missing some configurations required for using XA transactions.

Thanks.
Back to top
View user's profile Send private message
sebastianhirt
PostPosted: Wed Jul 13, 2005 11:30 pm    Post subject: Reply with quote

Yatiri

Joined: 07 Jun 2004
Posts: 620
Location: Germany

Hi,

Does this help you?

Quote:
Reason Code 2072 x'818'
MQRC_SYNCPOINT_NOT_AVAILABLE

Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to honor the request. If the queue manager does not support units of work, the SyncPoint queue-manager attribute will have the value MQSP_NOT_AVAILABLE. This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that coordinator requires an explicit call to start the unit of work, but the application has not issued that call prior to the MQGET, MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned.

* On AS/400, this reason codes means that AS/400 Commitment Control is not started, or is unavailable for use by the queue manager.

* On OS/390, this reason code does not occur.

Corrective action: Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate. On AS/400, ensure that Commitment Control has been started. If this reason code occurs after Commitment Control has been started, contact your systems programmer.
Back to top
View user's profile Send private message
vedantpatil
PostPosted: Thu Jul 14, 2005 9:41 pm    Post subject: MQJMS2007 Reply with quote

Novice

Joined: 10 Mar 2005
Posts: 19

We could resolve this issue.

As mentioned in the extract given by sebastianhirt as below

Quote:
This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that coordinator requires an explicit call to start the unit of work, but the application has not issued that call prior to the MQGET, MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned.


We are using WLS as an external coordinator for XA transactions and it required an explicit call to begin the unit of work before any MQGET calls.

Thanks for Help.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » JMSException: MQJMS2007
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.