Ibm Xms Error Codes
Contents |
(troubleshooting) Problem(Abstract) You have configured your compcode: 2, reason: 2393 WebSphere MQ (WMQ) client channel to use the client
Mqrc 2393
channel definition table(CCDT) with Secure Socket Layer(SSL) enabled. Using the amqsputc sample program mqconn ended with reason code 2393 to connect to your queue manager results in the following: 2393 MQRC_SSL_INITIALIZATION_ERROR Cause The key database modifications are not recognized by the http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.msc.doc/xms_cerrors.htm queue manager. Whenever changes are made to the certificates in the SSL key database of a WebSphere MQ server (after the SSL channel has been started), then the WMQ security information must be refreshed in order for the changes to be recognized. Resolving the problem http://www-01.ibm.com/support/docview.wss?uid=swg21236521 MQ V5.3 Recycle the queue manager to pick up the SSL configuration changes. MQ V6.0 / V7.0.x.x / V7.1.0.x / V7.5.0.x / 8.0.0.x Recycle the queue manager or use following runmqsc command to refresh SSL: Refresh Security type(ssl) Note: A "modification" of the key database constitutes any additions, or deletions of certificates within the key database, regardless of type (Signer Certificates, Intermediate Certificates, Personal Certificates, and so on.). Product Alias/Synonym WMQ MQ Document information More support for: WebSphere MQ SSL Software version: 5.3, 6.0, 7.0, 7.1, 7.5, 8.0 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Software edition: All Editions Reference #: 1236521 Modified date: 2014-12-02 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://stackoverflow.com/questions/20428155/ibm-xms-net-receiving-error-reason-code-2003 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 http://blog.robiii.nl/2012/01/websphere-mq-reason-codes.html Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a code 2 minute: Sign up IBM XMS .NET - Receiving Error - Reason Code 2003 up vote 1 down vote favorite We have .NET application which reads from various queues using the XMS API. For this particular application we read from 3 queues and every so often receive the error with reason code 2003 on 2 of the 3 queues. All 3 of reason code 2393 the queues are setup to have persistent messages. From everything I have researched, it appears that a long running transaction being rolled back causing this error. The reason for the long running transaction being rolled back appears to be from exhausted log space. When the transaction gets rolled back, it puts the messages we have previously read onto the queue so we end up reading duplicates. In the API, when we create our "Session" to read from the queues, we specify false for the transacted parameter. Therefore we never call "Commit" on the session. We also use the auto-acknowledge mode on the session. This leads me to believe that we don't have any sort of unit of work sepcified explicitly, but could there be an implicit transaction of some sort? The tricky part is that we are able to read fine on 1 of the 3 queues without ever receiving the error. Any ideas on where I could look next to troubleshoot such an issue? Creating the connection: cf.SetStringProperty(XMSC.WMQ_HOST_NAME, hostName); cf.SetIntProperty(XMSC.WMQ_PORT, port); cf.SetStringProperty(XMSC.WMQ_CHANNEL, channelName); cf.SetIntProperty(XMSC.WMQ_CONNECTION_MODE, XMSC.WMQ_CM_CLIENT_UNMANAGED); cf.SetStringProperty(XMSC.WMQ_QUEUE_MANAGER, managerName); cf.SetStringProperty(XMSC.WMQ_SSL_KEY_REPOSITORY, EncryptionSettings.SSLRepositoryPath); cf.SetStringProperty(XMSC.WMQ_SSL_CIPHER_SPEC, EncryptionSettings.CipherType); cf.SetIntProperty(XMSC.WMQ_FAIL
InnerException is beyond me. This page can be used to look up "ReasonCodes" (which is all the LinkedException provides in XMS.NET). The links in this page all lead to the specific help-page. CodeCode (hex)ReasonCodeDescription 00000RC0MQRC_NONE 9000384RC900MQRC_APPL_FIRST 99903E7RC999MQRC_APPL_LAST 200107D1RC2001MQRC_ALIAS_BASE_Q_TYPE_ERROR 200207D2RC2002MQRC_ALREADY_CONNECTED 200307D3RC2003MQRC_BACKED_OUT 200407D4RC2004MQRC_BUFFER_ERROR 200507D5RC2005MQRC_BUFFER_LENGTH_ERROR 200607D6RC2006MQRC_CHAR_ATTR_LENGTH_ERROR 200707D7RC2007MQRC_CHAR_ATTRS_ERROR 200807D8RC2008MQRC_CHAR_ATTRS_TOO_SHORT 200907D9RC2009MQRC_CONNECTION_BROKEN 201007DARC2010MQRC_DATA_LENGTH_ERROR 201107DBRC2011MQRC_DYNAMIC_Q_NAME_ERROR 201207DCRC2012MQRC_ENVIRONMENT_ERROR 201307DDRC2013MQRC_EXPIRY_ERROR 201407DERC2014MQRC_FEEDBACK_ERROR 201607E0RC2016MQRC_GET_INHIBITED 201707E1RC2017MQRC_HANDLE_NOT_AVAILABLE 201807E2RC2018MQRC_HCONN_ERROR 201907E3RC2019MQRC_HOBJ_ERROR 202007E4RC2020MQRC_INHIBIT_VALUE_ERROR 202107E5RC2021MQRC_INT_ATTR_COUNT_ERROR 202207E6RC2022MQRC_INT_ATTR_COUNT_TOO_SMALL 202307E7RC2023MQRC_INT_ATTRS_ARRAY_ERROR 202407E8RC2024MQRC_SYNCPOINT_LIMIT_REACHED 202507E9RC2025MQRC_MAX_CONNS_LIMIT_REACHED 202607EARC2026MQRC_MD_ERROR 202707EBRC2027MQRC_MISSING_REPLY_TO_Q 202907EDRC2029MQRC_MSG_TYPE_ERROR 203007EERC2030MQRC_MSG_TOO_BIG_FOR_Q 203107EFRC2031MQRC_MSG_TOO_BIG_FOR_Q_MGR 203307F1RC2033MQRC_NO_MSG_AVAILABLE 203407F2RC2034MQRC_NO_MSG_UNDER_CURSOR 203507F3RC2035MQRC_NOT_AUTHORIZED 203607F4RC2036MQRC_NOT_OPEN_FOR_BROWSE 203707F5RC2037MQRC_NOT_OPEN_FOR_INPUT 203807F6RC2038MQRC_NOT_OPEN_FOR_INQUIRE 203907F7RC2039MQRC_NOT_OPEN_FOR_OUTPUT 204007F8RC2040MQRC_NOT_OPEN_FOR_SET 204107F9RC2041MQRC_OBJECT_CHANGED 204207FARC2042MQRC_OBJECT_IN_USE 204307FBRC2043MQRC_OBJECT_TYPE_ERROR 204407FCRC2044MQRC_OD_ERROR 204507FDRC2045MQRC_OPTION_NOT_VALID_FOR_TYPE 204607FERC2046MQRC