Mq Error Code 2102
using Java or JMS in WMQ wmq Technote (troubleshooting) Problem(Abstract) When using WebSphere MQ (WMQ) Javaâ„¢ or JMS bindings mode connections on heavily loaded systems, a MQRC_RESOURCE_PROBLEM exception is thrown, with the stack showing the exception came from: Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2102 at com.ibm.mq.jmqi.JmqiWorkerThread.syncExec(JmqiWorkerThread.java:158) at com.ibm.mq.jmqi.local.LocalHconn.syncExec(LocalHconn.java:428) Cause When a bindings mode connection is made or used, the actual connection attempt or API call to the local queue manager is delegated to a JmqiWorkerThread. The submitter will wait for 20 seconds (default value) for the worker thread to start the assigned work - if the thread has not started after this timeout period, an exception will be thrown with the reason code MQRC_RESOURCE_PROBLEM. Resolving the problem Usually this is due to a very high load on the JVM, so time could not be allocated to the JmqiWorkerThread in the specfied time period. It is possible to tune this timeout period to allow extra time for the JmqiWorkerThreads to start and avoid the MQRC_RESOURCE_PROBLEM exceptions. The timeout period for which a worker thread will be waited can be configured with the property: -Dcom.ibm.mq.jmqi.threadWaitTimeout=
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 MQ error 2102(Resource_Prob in datastage) up vote 0 http://www-01.ibm.com/support/docview.wss?uid=swg21640627 down vote favorite When datastage Job is trying to put the message in queue, The error message comes, I guess this may be the issue with size of file which we were trying to post, which were around 3MB, but when we tried with around 2MB size, it got posted succesfuly in the queue. Can somebody guide on this. websphere-mq share|improve this question asked Oct 8 '13 http://stackoverflow.com/questions/19246950/mq-error-2102resource-prob-in-datastage at 11:50 Ishan Mahajan 155 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted MQ error 2102 indicates "insufficient system resources to complete the call successfully". As per your question, you get this error when you post bigger message. So, it makes me believe that your server is running out of space which is causing this issue. share|improve this answer answered Oct 8 '13 at 13:52 nitgeek 860617 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged websphere-mq or ask your own question. asked 3 years ago viewed 576 times active 3 years ago Related 2Defining WebSphere MQ administrative subscriptions1Determine if an MQ queue is an error queue or not2Websphere MQ Explorer & AMQ8077 Errors3How does WMQ exchange DLQ information between remote and local queue managers?2Hermes JMS cannot connect to Websphere MQ 7.1 (2035 error)1Unconvertable
RSS Feed - WebSphere http://www.mqseries.net/phpBB2/viewtopic.php?t=12197&highlight=2102 MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » Workflow Engines - https://www.imwuc.org/blog/ibm-websphere-mq-reason-code-list-/-mq-reason-codes-/-websphere-mq-error-codes-/-mq-error-messages IBM MQ Workflow & Business Process Choreographer » MQRC 2102 (MQRC_RESOURCE_PROBLEM) during workflow logon MQRC 2102 (MQRC_RESOURCE_PROBLEM) during workflow logon « View previous topic :: View next topic » Author Message muralihegde Posted: Thu Dec 04, 2003 4:20 am Post subject: MQRC 2102 (MQRC_RESOURCE_PROBLEM) during workflow logon CenturionJoined: 30 Apr 2002Posts: 102 Hi All, We have the following environment. MQ mq error Series V 5.3.0 MQ Workflow V 3.4.0 WAS V5.0 AIX 5.1 When a workflow logon call is executed from an application deployed on WAS, we get the following error. FmcException: Can not connect to queue manager MQRC 2102 (MQRC_RESOURCE_PROBLEM) The corresponding MQ Error Log file for the queue manager at the location /var/mqm/qmgrs/FMCQM/errors/AMQERR01.LOG has the following error entry. ----- amqxstex.c : 1563 ------------------------------------------------------- 12/04/03 12:34:30 AMQ6207: Failed to attach shared memory segment mq error code as Segment table is Full. EXPLANATION: When running in native mode an application may attach only 10 shared memory segments. The application which issued this message attempted to exceed this number. By setting the environment variable EXTSHM=ON this limit can be removed. Further explanation on using this variable and other options available, may be found in the documentation. ACTION: Either reduce the number of segments to which your application needs to attach or set the EXTSHM=ON variable in your environment before starting the application. ----- amqxstex.c : 1563 ------------------------------------------------------- We have set the environment variable EXTSHM=ON for the profiles of the following users. 1. workflow user id (fmc) used to start queue manager FMCQM and workflow server 2. mq user id (mqm) used to start the queue manger WASQMGR, queue manager for WAS. 3. root, the user Id used to start the WAS application server. But still we get the above error. Please note that the above problem does NOT occur when 1. We use the sample HelloApplicaiton on AIX to connect to workflow server. 2. We connect to the Workflow server though a Workflow web client running on a different PC ( different WAS server) 3. Use a default Windows Client for Workflow running on a different PC. Looks like the problem oBlog IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages Karthick Karthikeyan MQRC_* (Reason Codes) MQRC_NONE 0 X'00000000' MQRC_APPL_FIRST 900 X'00000384' MQRC_APPL_LAST 999 X'000003E7' MQRC_ALIAS_BASE_Q_TYPE_ERROR 2001 X'000007D1' MQRC_ALREADY_CONNECTED 2002 X'000007D2' MQRC_BACKED_OUT 2003 X'000007D3' MQRC_BUFFER_ERROR 2004 X'000007D4' MQRC_BUFFER_LENGTH_ERROR 2005 X'000007D5' MQRC_CHAR_ATTR_LENGTH_ERROR 2006 X'000007D6' MQRC_CHAR_ATTRS_ERROR 2007 X'000007D7' MQRC_CHAR_ATTRS_TOO_SHORT 2008 X'000007D8' MQRC_CONNECTION_BROKEN 2009 X'000007D9' MQRC_DATA_LENGTH_ERROR 2010 X'000007DA' MQRC_DYNAMIC_Q_NAME_ERROR 2011 X'000007DB' MQRC_ENVIRONMENT_ERROR 2012 X'000007DC' MQRC_EXPIRY_ERROR 2013 X'000007DD' MQRC_FEEDBACK_ERROR 2014 X'000007DE' MQRC_GET_INHIBITED 2016 X'000007E0' MQRC_HANDLE_NOT_AVAILABLE 2017 X'000007E1' MQRC_HCONN_ERROR 2018 X'000007E2' MQRC_HOBJ_ERROR 2019 X'000007E3' MQRC_INHIBIT_VALUE_ERROR 2020 X'000007E4' MQRC_INT_ATTR_COUNT_ERROR 2021 X'000007E5' MQRC_INT_ATTR_COUNT_TOO_SMALL 2022 X'000007E6' MQRC_INT_ATTRS_ARRAY_ERROR 2023 X'000007E7' MQRC_SYNCPOINT_LIMIT_REACHED 2024 X'000007E8' MQRC_MAX_CONNS_LIMIT_REACHED 2025 X'000007E9' MQRC_MD_ERROR 2026 X'000007EA' MQRC_MISSING_REPLY_TO_Q 2027 X'000007EB' MQRC_MSG_TYPE_ERROR 2029 X'000007ED' MQRC_MSG_TOO_BIG_FOR_Q 2030 X'000007EE' MQRC_MSG_TOO_BIG_FOR_Q_MGR 2031 X'000007EF' MQRC_NO_MSG_AVAILABLE 2033 X'000007F1' MQRC_NO_MSG_UNDER_CURSOR 2034 X'000007F2' MQRC_NOT_AUTHORIZED 2035 X'000007F3' MQRC_NOT_OPEN_FOR_BROWSE 2036 X'000007F4' MQRC_NOT_OPEN_FOR_INPUT 2037 X'000007F5' MQRC_NOT_OPEN_FOR_INQUIRE 2038 X'000007F6' MQRC_NOT_OPEN_FOR_OUTPUT 2039 X'000007F7' MQRC_NOT_OPEN_FOR_SET 2040 X'000007F8' MQRC_OBJECT_CHANGED 2041 X'000007F9' MQRC_OBJECT_IN_USE 2042 X'0000