| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQCONN failed, CC=2 RC=2059 depending on id started QMgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| kpferg |
 Posted: Wed Feb 25, 2004 8:33 am Post subject: MQCONN failed, CC=2 RC=2059 depending on id started QMgr |
 |
|
Newbie
Joined: 14 Jan 2002
Posts: 2
Location: RTP, NC
|
I have a C PCF program I have developed to gather data about Queue Managers. I have encountered an interesting situation and haven't been able to track down a solution.
My program always runs as MUSR_MQADMIN. When I manually start the QMgr as an administrator in the mqm group I have no problem connecting and gathering my information. The problem comes when I start the QMgr as MUSR_MQADMIN (either automatically on system boot, or through a task that runs as MUSR_MQADMIN). The error comes in trying to connect: MQCONN failed, CC=2 RC=2059. FYI: I have only seen this problem on Win2000, Unix runs fine. Just to cover my bases I have made sure the QMgr is running and the command server is running and Listener is running. Basically everything is the same except the user who started the QMgr.
I tried tracing the error but haven't come to a solution:
::From AMQ1680.TRC::
| Code: |
Version : 530 Level : p000-L020617
.
.
.
0095CF6F 17:29:06.616817 1680.1 -----{ xstStorageRequest
0095CF70 17:29:06.616839 1680.1 ------{ xstServerRequest
0095D528 17:29:15.835429 1680.1 ------} xstServerRequest (rc=OK)
0095D529 17:29:15.835463 1680.1 -----}! xstStorageRequest (rc=xecF_E_UNEXPECTED_SYSTEM_RC)
0095D52A 17:29:15.835550 1680.1 ----}! xstAttachServer (rc=xecF_E_UNEXPECTED_SYSTEM_RC)
0095D52B 17:29:15.835613 1680.1 ----{ xcsDisconnectSharedMemSet
0095D52C 17:29:15.835659 1680.1 About to disconnect set 1::0::0-292
0095D52D 17:29:15.835682 1680.1 -----{ xcsRequestThreadMutexSem
0095D52E 17:29:15.835704 1680.1 -----} xcsRequestThreadMutexSem (rc=OK)
0095D52F 17:29:15.835721 1680.1 -----{ xcsFreeMem
0095D530 17:29:15.835745 1680.1 component:24 pointer:00317CF0
0095D531 17:29:15.835767 1680.1 -----} xcsFreeMem (rc=OK)
0095D532 17:29:15.835791 1680.1 This set has 1 connections left (including us)
0095D533 17:29:15.835810 1680.1 -----{ xcsFreeMem
0095D534 17:29:15.835833 1680.1 component:24 pointer:00317C98
0095D535 17:29:15.835852 1680.1 -----} xcsFreeMem (rc=OK)
0095D536 17:29:15.835877 1680.1 -----{ xcsGetSetConnectCount
0095D537 17:29:15.835896 1680.1 ------{ xstGetExtentConnectCount
0095D538 17:29:15.835912 1680.1 ------}! xstGetExtentConnectCount (rc=xecI_S_NOT_INIT)
0095D539 17:29:15.835972 1680.1 Set has 0 connections
0095D53A 17:29:15.835993 1680.1 -----}! xcsGetSetConnectCount (rc=xecI_S_NOT_INIT)
0095D53B 17:29:15.836037 1680.1 -----{ xstDisconnectExtent
0095D53C 17:29:15.836053 1680.1 ------{ xcsRequestThreadMutexSem
0095D53D 17:29:15.836071 1680.1 ------} xcsRequestThreadMutexSem (rc=OK)
0095D53E 17:29:15.836123 1680.1 ------{ xcsReleaseThreadMutexSem
0095D53F 17:29:15.836147 1680.1 ------} xcsReleaseThreadMutexSem (rc=OK)
0095D540 17:29:15.836163 1680.1 -----} xstDisconnectExtent (rc=OK)
0095D541 17:29:15.836181 1680.1 -----{ xcsReleaseThreadMutexSem
0095D542 17:29:15.836199 1680.1 -----} xcsReleaseThreadMutexSem (rc=OK)
0095D543 17:29:15.836214 1680.1 ----} xcsDisconnectSharedMemSet (rc=OK)
0095D544 17:29:15.836231 1680.1 ----{ xcsFreeMem
0095D545 17:29:15.836256 1680.1 component:24 pointer:00317AE0
0095D546 17:29:15.836278 1680.1 ----} xcsFreeMem (rc=OK)
0095D547 17:29:15.836294 1680.1 ----{ xcsDestroyThreadMutexSem
0095D548 17:29:15.836319 1680.1 ----} xcsDestroyThreadMutexSem (rc=OK)
0095D549 17:29:15.836338 1680.1 ----{ xcsDestroyThreadMutexSem
0095D54A 17:29:15.836361 1680.1 ----} xcsDestroyThreadMutexSem (rc=OK)
0095D54B 17:29:15.836380 1680.1 ----{ xcsFreeMem
0095D54C 17:29:15.836404 1680.1 component:24 pointer:003178E8
0095D54D 17:29:15.836424 1680.1 ----} xcsFreeMem (rc=OK)
0095D54E 17:29:15.836440 1680.1 ---}! xcsAttachSharedSubpool (rc=xecX_E_SUBPOOL_INVALID)
0095D54F 17:29:15.836491 1680.1 --}! xcsConnectSharedSubpool (rc=xecX_E_SUBPOOL_INVALID)
0095D550 17:29:15.836544 1680.1 --{ TermPrivateServices
0095D551 17:29:15.836577 1680.1 ---{ xxxTerminate
0095D552 17:29:15.836597 1680.1 ---} xxxTerminate (rc=OK)
0095D553 17:29:15.836613 1680.1 --} TermPrivateServices (rc=OK)
|
::from AMQERR01.LOG::
| Code: |
02/24/2004 17:29:06
AMQ6119: An internal WebSphere MQ error has occurred (Failed to open handle on
process 1680 - (5))
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 626 --------------------------------------------------------
02/24/2004 17:29:09
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QM(1).
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2072.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 660 -------------------------------------------------------- |
Thanks for any insight into this,
-KP  |
|
| Back to top |
|
 |
| Missam |
| Posted: Wed Feb 25, 2004 10:38 pm Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
May be this is reason you are on Windows2000.Recreating your mqm group and assigning it back to MUSR_MQADMIN may solve your problem.
There is an Interesting Topic on this particular scenerio in System Administration Guide chapter 10)websphere MQ security and a section named Guidelines for Windows2000.just refer it,that may help you |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Feb 26, 2004 3:01 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
1. apply a fixpack
2. If problem persists, give the MUSR_MQADMIN the 'Debug programs' local user right |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
