| Author |
Message
|
| muralihegde |
 Posted: Thu Dec 04, 2003 4:20 am Post subject: MQRC 2102 (MQRC_RESOURCE_PROBLEM) during workflow logon |
 |
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi All,
We have the following environment.
MQ 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 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 occurs only when the logon call is made from an application running under WAS running on the same AIX box (but different queue manager).
As with all software projects, it is critical that we solve this problem immediately to move ahead  ..
Any help, suggestion is greatly appreciated..
-Murali |
|
| Back to top |
|
 |
| ben harris |
| Posted: Thu Apr 01, 2004 10:42 am Post subject: |
|
|
Novice
Joined: 25 Jun 2003
Posts: 19
|
Have you found a solution?
I am experiencing the same problem when I try to connect via a web client...here is my servlet.log:
2004-04-01 18:10:07.967 http9280-Processor4: Servlet initialized.
2004-04-01 18:10:07.968 http9280-Processor4: logon called.
2004-04-01 18:10:07.969 http9280-Processor4: userID: ADMIN
2004-04-01 18:10:07.969 http9280-Processor4: mode: null
2004-04-01 18:10:07.972 http9280-Processor4: Locating system '' in group ''.
2004-04-01 18:10:07.972 http9280-Processor4: Binding agent 'MQWFAGENT' for T01DV3WC
2004-04-01 18:10:08.374 http9280-Processor4: Agent bound.
2004-04-01 18:10:08.421 http9280-Processor4: Logging on for userid ADMIN
2004-04-01 18:10:08.496 http9280-Processor4: doGet (logon): com.ibm.workflow.servlet.client.ClientException: FMC00013E Communication error - Failing Action: Connect_t_to_QM, Reason Code: 2102, Failing Object: MQWF003B.
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drvp/lbld/v340/aix/src/fmcjcesv.cxx, line 2161
Error Message : FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2102, Failing Object: MQWF003B.
Nested Exception : None
I have also exported EXTSHM=ON in my env before starting my engine and queue managers.
Ben. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Apr 01, 2004 11:07 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
may be this helps: (taken from IBM site)
| Quote: |
Had the customer test setting EXTSHM=ON. We found that if he sets EXTSHM=ON for the QMGR, but not in the environment where he starts his java application, it still failed with the RC=2102. If cust sets the EXTSHM=ON for the application, then it connected successfully and all was OK. He then tried setting EXTSHM=ON for the application and not for the qmgr and it still works OK.
EXTSHM=ON should be set for all MQ processes and applications. In fact, the qmgr performs some trickery to ensure it is always set for its own processes, but that introduces unnecessary complication and so the recommendation, with MQ 5.3, is to set EXTSHM=ON as widely as possible.
With MQ 5.3, the setting of IPCCBaseAddress can be safely removed from the ini files, since it is no longer used and is ignored if present.
|
_________________
-Ratan |
|
| Back to top |
|
|
| mqworkflow |
| Posted: Thu Apr 01, 2004 1:21 pm Post subject: |
|
|
Apprentice
Joined: 23 Feb 2004
Posts: 32
|
Did you guys set up the parameter Ratan is talking about.
"IPCCBASEADDRESS = 12" in mqs.ini file in var/mqm/qmgr directory.
This is required for MQ 5.2 but I think it wouldnt hurt for 5.3 though.
Actually you can find this in the Installation Guide.
Thanks
mqwf |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sat Dec 19, 2009 3:06 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Hi,
I got the similar kind of error while getting the msg from the queue.
MQGET(QMGR='Q3SCIB05',Q='QL.KP.KPFS.DEMG.LFS') failed: reason code 2102.
display qlocal(QL.KP.KPFS.DEMG.LFS)
2 : display qlocal(QL.KP.KPFS.DEMG.LFS)
AMQ8409: Display Queue details.
DESCR( ) PROCESS( )
BOQNAME( ) INITQ( )
TRIGDATA( ) CLUSTER( )
CLUSNL( ) QUEUE(QL.KP.KPFS.DEMG.LFS)
CRDATE(2005-12-01) CRTIME(16.47.5
ALTDATE(2005-12-01) ALTTIME(16.47.5
GET(ENABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(YES)
MAXDEPTH(200000) MAXMSGL(50194304)
BOTHRESH(999999999) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(FIFO) RETINTVL(999999999)
USAGE(NORMAL) NOTRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(5) QDPMAXEV(ENABLED)
QDPHIEV(ENABLED) QDPLOEV(DISABLED)
QSVCINT(10000) QSVCIEV(HIGH)
DISTL(NO) NPMCLASS(NORMAL)
DEFTYPE(PREDEFINED) TYPE(QLOCAL)
SCOPE(QMGR) DEFBIND(OPEN)
IPPROCS(0) OPPROCS(1)
CURDEPTH(0)
where as when i browsed the queue local.. then current depth was 0 and OPPROC is 1, where as IPPROC is 0.
Dont even find any errors on queuemanager error log.
Pls suggest.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sat Dec 19, 2009 5:03 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
mqrc 2102
2102 0x00000836 MQRC_RESOURCE_PROBLEM
and i have checked the resource as
df | grep Q3SCIB05
/dev/lv1913_q3scib05 5373952 507768 91% 1153 1% /MQHA1913/Q3SCIB05/data
as 91% is used space., that could be the reason for the issue. But cant bet on that.
Anybody has faced such problem ?
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sun Dec 20, 2009 2:41 am Post subject: Re: MQRC 2102 (MQRC_RESOURCE_PROBLEM) during workflow logon |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| shashivarungupta wrote: |
I got the similar kind of error while getting the msg from the queue.
MQGET(QMGR='Q3SCIB05',Q='QL.KP.KPFS.DEMG.LFS') failed: reason code 2102. |
Aside from the same reason code, this doesn't really look like the same issue muralihegde reported about 6 years ago. Perhaps it would have been better to start a new topic, (in the correct forum), rather than reopen an old one.
A little more information would help. What platform? What version of MQ? What MQGET application? Are there similar errors with other queues, or just this one? When was the last FFST, what did it say, and had the qmgr been restarted since then? |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sun Dec 20, 2009 11:15 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
ya.. iwas thinking to post the issue as a new post.. i'll do that. you'll see it soon there..thanks for the reply though. 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
