Mq Error 2072
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Getting 'MQCC_FAILED' reason '2072' 'MQRC_SYNCPOINT_NOT_AVAILABLE' while attempting to send a message up vote 1 down vote favorite I have an MDB (mdbA) in JBoss 5.1 GA which listens to an MQ 7.0 queue. After reception, the message is persisted to a MySQL database and I would like to send the message to another queue (queueB) and then continue processing the message in mdbA which does some more inserts and sends a message to a HornetQ. All works fine for the first message and I see the message in Database as well as queueB and hornetQ. For all subsequent messages, the "send to queueB" results in 'MQRC_SYNCPOINT_NOT_AVAILABLE'error 2072. My mdbA has the following annotations. @TransactionAttribute (TransactionAttributeType.REQUIRED) @Service Please let me know if I need to provide more information. Could someone please assist? websphere-mq hornetq jboss-messaging share|improve this question edited Jan 14 '14 at 4:19 asked Jan 13 '14 at 3:04 Jeet 114113 Maybe this is useful: stevemelan.wordpress.com/2014/05/22/… –uselpa May 22 '14 at 19:02 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Solved a similar issue in WebLogic where the MDB itself was annotated @TransactionManagement(TransactionManagementType.BEAN) and choosing instead @TransactionManagement(TransactionManagementType.CONTAINER) solved the issue, with no Transaction attribute on methods, hence default REQUIRED. In fact, sound MDB's would likely delegate transactions to the container and not attempt to control them explicitly in code. If you use BEAN management type and do not open explicitly a transaction context, no sy
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Multiphase Commit » 2072/SYNCPOINT error during XA transaction on JBoss 2072/SYNCPOINT error during XA transaction on JBoss « View previous topic :: View next topic » Author Message edward2013 Posted: Wed Jan 23, 2013 5:23 pm Post subject: 2072/SYNCPOINT error during XA transaction on JBoss NewbieJoined: 23 Jan 2013Posts: 1 Hi, I've configured a JBoss server to import several WMQ queues using the WMQ JCA resource adapter. To do this, http://stackoverflow.com/questions/21083210/getting-mqcc-failed-reason-2072-mqrc-syncpoint-not-available-while-attempt I configured afrom my blog at BEA dev2dev, which is soon will http://www.jroller.com/eu/entry/resolving_webspheremq_reason_codes_out be decommissioned because of the merging with Oracle developer network. One who ever dealt with MQSeries knows that extracting information out of WebSphereMQ (MQSeries) exceptions is a http://middleware-wmq-wmb.blogspot.com/2013/01/mq-reason-code-list.html key for understanding cause of the problem. Unfortunately, implementation of MQSeries JMS client doesn't do a good job about explaining error details and you have explicitly get mq error it from the linked exception. ... } catch(JMSException ex) { Exception exx = ex.getLinkedException() != null ? ex.getLinkedException() : ex; String msg = "JMS error: "+exx.getMessage(); logger.error(msg, exx); ... } But even then errors you would see in the log are quite cryptic: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2072 That means nothing to mq error 2072 the most of the support stuff except maybe rare MQSeries guru who can tell meaning of these reason codes from the top of the head or at least know where to look at in the MQSeries reference documentation. For instance the above 2072 reason code correspond to an infamous "Syncpoint support not available" (MQRC_SYNCPOINT_NOT_AVAILABLE) error that cause lot of troubles before WLS 8.1 introduced Wrapped JMS Connection Factory for the Foreign JMS providers. It is a real time saver feature to actually resolve these error codes to more meaningful names. An obvious approach would be to grab the list of reason codes from an MQSeries manual, package it as a property file with the Java code and manually resolve the error message. ... } catch(JMSException ex) { Exception exx = ex.getLinkedException() != null ? ex.getLinkedException() : ex; String msg = "JMS error: "+exx.getMessage(); if(exx instanceof MQException) { MQException mqex = (MQException) exx; msg += " " + MQ_REASON_CODES.get(mqex.reasonCode); } logger.err
as default browser and unfortunately I can't read IBM info center from it. Reason code list The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: An explanation of the circumstances that have caused the code to be raised The associated completion code Suggested programmer actions in response to the code 0 (0000) (RC0): MQRC_NONE 900 (0384) (RC900): MQRC_APPL_FIRST 999 (03E7) (RC999): MQRC_APPL_LAST 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED 2003 (07D3) (RC2003): MQRC_BACKED_OUT 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR 2012 (07DC) (RC2012): MQRC_ENVIRONMENT_ERROR 2013 (07DD) (RC2013): MQRC_EXPIRY_ERROR 2014 (07DE) (RC2014): MQRC_FEEDBACK_ERROR 2016 (07E0) (RC2016): MQRC_GET_INHIBITED 2017 (07E1) (RC2017): MQRC_HANDLE_NOT_AVAILABLE 2018 (07E2) (RC2018): MQRC_HCONN_ERROR 2019 (07E3) (RC2019): MQRC_HOBJ_ERROR 2020 (07E4) (RC2020): MQRC_INHIBIT_VALUE_ERROR 2021 (07E5) (RC2021): MQRC_INT_ATTR_COUNT_ERROR 2022 (07E6) (RC2022): MQRC_INT_ATTR_COUNT_TOO_SMALL 2023 (07E7) (RC2023): MQRC_INT_ATTRS_ARRAY_ERROR 2024 (07E8) (RC2024): MQRC_SYNCPOINT_LIMIT_REACHED 2025 (07E9) (RC2025): MQRC_MAX_CONNS_LIMIT_REACHED 2026 (07EA) (RC2026): MQRC_MD_ERROR 2027 (07EB) (RC2027): MQRC_MISSING_REPLY_TO_Q 2029 (07ED) (RC2029): MQRC_MSG_TYPE_ERROR 2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q 2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR 2033 (07F1) (RC2033): MQRC_NO_MSG_AVAILABLE 2034 (07F2) (RC2034): MQRC_NO_MSG_UNDER_CURSOR 2035 (07F3) (RC2035): MQRC_NOT_AUTHORIZED 2036 (07F4) (RC2036): MQRC