| Author |
Message
|
| Steffi |
 Posted: Wed Nov 30, 2005 7:38 am Post subject: WMQ 6.0 Server - Creation of QueueManager hangs |
 |
|
Newbie
Joined: 30 Nov 2005
Posts: 5
|
Hi,
I have installed WebSphere MQ Server 6.0 on a Windows Server 2003.
In the "Prepare WebSphere MQ Wizard", I had to enter a special domain user account because the Domain Controller is a Windows Server 2003 (as described in the installation instructions).
When I try to set up the default configuration, the processor load increases to 100% (especially because of process amqzxma0.exe) and the configuration process hangs.
Even if I let it run several hours, the wizard is not able to set up the default Queue Manager and the default cluster.
But a few minutes after the configuration process has started, the event log shows the following messages:
Warning:
"WebSphere MQ semaphore is busy.
WebSphere MQ was unable to acquire a semaphore within the normal timeout period of 0 minutes. MQ will continue to wait for access. If the situation does not resolve itself and you suspect that your system is locked then investigate the process which owns the semaphore.
The PID of this process will be documented in the accompanying FFST."
Warning:
"An internal WebSphere MQ error has occurred on queue manager QM_vsserver. An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 2720.
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."
Error:
"An internal WebSphere MQ error has occurred.
An error has been detected, and the MQ error recording routine has been called. Details of the error have been stored at C:\Program Files\IBM\WebSphere MQ\errors\AMQ2720.0.FDC. A synopsis is given in the data section below. 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."
Does anybody know what causes this problem or how to solve it?
Thanks in advance,
Steffi |
|
| Back to top |
|
 |
| JT |
| Posted: Wed Nov 30, 2005 9:45 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Post the top two sections of the FDC. |
|
| Back to top |
|
|
| Steffi |
| Posted: Wed Nov 30, 2005 11:31 pm Post subject: |
|
|
Newbie
Joined: 30 Nov 2005
Posts: 5
|
Hi,
thank you for your reply.
The first sections of the FDC look like that:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mi November 30 16:21:22 W. Europe Standard Time 2005 |
| Host Name :- VSSERVER (Windows Ver 5.2 Build 3790: ) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY337101 |
| Application Name :- MQM |
| Component :- xllLongLockRequest |
| SCCS Info :- lib/cs/pc/winnt/amqxsemn.c, 1.97 |
| Line Number :- 1632 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- administrator |
| Process Name :- C:\Program Files\IBM\Eclipse SDK30\eclipse\jre\bin |
| \javaw.exe |
| Process :- 00002720 |
| Thread :- 00000005 |
| QueueManager :- QM_vsserver |
| ConnId(1) IPCC :- 11 |
| Major Errorcode :- xecL_W_LONG_LOCK_WAIT |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6150 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6150: WebSphere MQ-Semaphor ist belegt. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
amqjxcsa.wmqNativeCall
amqjxcsa.jxcGetCommandServerStatus
MQCONNX
trmzstMQCONNX
zstMQCONNX
zstMQConnect
ziiMQCONN
ziiConnectToAgent
zcpAttachPipe
xllLongLockRequest
xcsFFST
MQM Trace History
------------} xcsGetMem rc=OK
-----------} xstAttachSharedMemSet rc=OK
-----------{ xcsReleaseThreadMutexSem
-----------} xcsReleaseThreadMutexSem rc=OK
----------} xcsConnectSharedMemSet rc=OK
----------{ xcsDestroySubpoolIfInvalid
----------} xcsDestroySubpoolIfInvalid rc=OK
----------{ xcsAttachSetExtents
----------} xcsAttachSetExtents rc=OK
---------} xcsAttachSharedSubpool rc=OK
--------} xcsConnectSharedSubpool rc=OK
--------{ xcsGetEnvironmentString
--------} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
--------{ xcsReleaseThreadMutexSem
--------} xcsReleaseThreadMutexSem rc=OK
-------} xcsInitialize rc=OK
-------{ zutConnectConfig
--------{ xcsLookupNamedMemBlock
---------{ xcsEnumerateQuickCellBlock
----------{ xcsGetMem
----------} xcsGetMem rc=OK
---------} xcsEnumerateQuickCellBlock rc=OK
---------{ xcsFreeMem
---------} xcsFreeMem rc=OK
--------} xcsLookupNamedMemBlock rc=OK
--------{ xcsGetMem
--------} xcsGetMem rc=OK
-------} zutConnectConfig rc=OK
-------{ xcsTerminate
--------{ xcsRequestThreadMutexSem
--------} xcsRequestThreadMutexSem rc=OK
--------{ xihCheckThreadList
--------} xihCheckThreadList rc=OK
--------{ xcsCacheSharedSubpool
---------{ xcsGetMem
---------} xcsGetMem rc=OK
--------} xcsCacheSharedSubpool rc=OK
--------{ xcsDisconnectSharedSubpool
---------{ xcsDettachSharedSubpool
----------{ xcsDisconnectSharedMemSet
-----------{ xcsRequestThreadMutexSem
-----------} xcsRequestThreadMutexSem rc=OK
-----------{ xcsFreeMem
-----------} xcsFreeMem rc=OK
-----------{ xcsFreeMem
-----------} xcsFreeMem rc=OK
-----------{ xcsReleaseThreadMutexSem
-----------} xcsReleaseThreadMutexSem rc=OK
----------} xcsDisconnectSharedMemSet rc=OK
----------{ xstDisconnectExtent
-----------{ xcsRequestThreadMutexSem
-----------} xcsRequestThreadMutexSem rc=OK
-----------{ xcsReleaseThreadMutexSem
-----------} xcsReleaseThreadMutexSem rc=OK
----------} xstDisconnectExtent rc=OK
----------{ xcsFreeMem
----------} xcsFreeMem rc=OK
----------{ xcsDestroyThreadMutexSem
-----------{ xcsCloseHandle
-----------} xcsCloseHandle rc=Unknown(1)
----------} xcsDestroyThreadMutexSem rc=OK
----------{ xcsDestroyThreadMutexSem
-----------{ xcsCloseHandle
-----------} xcsCloseHandle rc=Unknown(1)
----------} xcsDestroyThreadMutexSem rc=OK
----------{ xcsFreeMem
----------} xcsFreeMem rc=OK
---------} xcsDettachSharedSubpool rc=OK
---------{ xllDropSubpoolHandles
---------} xllDropSubpoolHandles rc=OK
--------} xcsDisconnectSharedSubpool rc=OK
--------{ xcsReleaseThreadMutexSem
--------} xcsReleaseThreadMutexSem rc=OK
-------} xcsTerminate rc=OK
------} zstInitCS rc=OK
------{ zutQueryValue
------} zutQueryValue rc=OK
------{ zutQueryValue
------} zutQueryValue rc=OK
------{ ztmInitialise
-------{ xcsCreateThreadMutexSem
-------} xcsCreateThreadMutexSem rc=OK
------} ztmInitialise rc=OK
------{ zstInsertPCD
-------{ xcsRegComp
-------} xcsRegComp rc=OK
-------{ xcsGetMem
-------} xcsGetMem rc=OK
-------{ zstGetApplIds
--------{ xcsUpdateThreadUserDetails
---------{ xcsGetNTOwnerSid
---------} xcsGetNTOwnerSid rc=OK
--------} xcsUpdateThreadUserDetails rc=OK
--------{ xcsQueryValueForSubpool
--------} xcsQueryValueForSubpool rc=xecU_W_TRUNCATED
--------{ xcsQueryValueForSubpool
--------} xcsQueryValueForSubpool rc=OK
--------{ xcsQueryValueForSubpool
--------} xcsQueryValueForSubpool rc=OK
--------{ xcsQueryValueForSubpool
--------} xcsQueryValueForSubpool rc=xecU_W_TRUNCATED
--------{ zutQueryThreadId
--------} zutQueryThreadId rc=OK
-------} zstGetApplIds rc=OK
------} zstInsertPCD rc=OK
------{ xcsRegisterDestructor
-------{ xcsGetMem
-------} xcsGetMem rc=OK
-------{ xcsRequestThreadMutexSem
-------} xcsRequestThreadMutexSem rc=OK
-------{ xcsReleaseThreadMutexSem
-------} xcsReleaseThreadMutexSem rc=OK
------} xcsRegisterDestructor rc=OK
------{ zutLoadApiExits
-------{ zutQueryValue
-------} zutQueryValue rc=OK
------} zutLoadApiExits rc=OK
------{ ziiInitialise
------} ziiInitialise rc=OK
------{ ziiMQCONN
-------{ zutUnlockLocalThreads
--------{ xcsReleaseThreadMutexSem
--------} xcsReleaseThreadMutexSem rc=OK
-------} zutUnlockLocalThreads rc=OK
-------{ ziiConnectToAgent
--------{ ziiCheckECRunning
--------} ziiCheckECRunning rc=OK
--------{ xcsInitialize
---------{ xcsUpdateThreadUserDetails
----------{ xcsGetNTOwnerSid
----------} xcsGetNTOwnerSid rc=OK
---------} xcsUpdateThreadUserDetails rc=OK
---------{ xcsRequestThreadMutexSem
---------} xcsRequestThreadMutexSem rc=OK
---------{ xihCheckThreadList
---------} xihCheckThreadList rc=OK
---------{ xcsInitGlobalSecurityData
---------} xcsInitGlobalSecurityData rc=OK
---------{ xcsConnectSharedSubpool
----------{ xcsAttachSharedSubpool
-----------{ xcsGetMem
-----------} xcsGetMem rc=OK
-----------{ xcsCreateThreadMutexSem
-----------} xcsCreateThreadMutexSem rc=OK
-----------{ xcsCreateThreadMutexSem
-----------} xcsCreateThreadMutexSem rc=OK
-----------{ xcsGetMem
-----------} xcsGetMem rc=OK
-----------{ xcsConnectSharedMemSet
------------{ xcsRequestThreadMutexSem
------------} xcsRequestThreadMutexSem rc=OK
------------{ xcsRequestThreadMutexSem
------------} xcsRequestThreadMutexSem rc=OK
------------{ xcsReleaseThreadMutexSem
------------} xcsReleaseThreadMutexSem rc=OK
------------{ xstAttachSharedMemSet
-------------{ xstConnectExtent
--------------{ xcsRequestThreadMutexSem
--------------} xcsRequestThreadMutexSem rc=OK
--------------{ xcsReleaseThreadMutexSem
--------------} xcsReleaseThreadMutexSem rc=OK
-------------} xstConnectExtent rc=OK
-------------{ xcsGetMem
-------------} xcsGetMem rc=OK
-------------{ xcsGetMem
-------------} xcsGetMem rc=OK
------------} xstAttachSharedMemSet rc=OK
------------{ xcsReleaseThreadMutexSem
------------} xcsReleaseThreadMutexSem rc=OK
-----------} xcsConnectSharedMemSet rc=OK
-----------{ xcsDestroySubpoolIfInvalid
-----------} xcsDestroySubpoolIfInvalid rc=OK
-----------{ xstAttachServer
------------{ xstStorageRequest
-------------{ xstServerRequest
-------------} xstServerRequest rc=OK
------------} xstStorageRequest rc=OK
-----------} xstAttachServer rc=OK
-----------{ xcsAllocateQuickCell
-----------} xcsAllocateQuickCell rc=OK
-----------{ xcsAttachSetExtents
------------{ xstConnectExtent
-------------{ xcsRequestThreadMutexSem
-------------} xcsRequestThreadMutexSem rc=OK
-------------{ xstStorageRequest
--------------{ xstServerRequest
--------------} xstServerRequest rc=OK
-------------} xstStorageRequest rc=OK
-------------{ xcsReleaseThreadMutexSem
-------------} xcsReleaseThreadMutexSem rc=OK
------------} xstConnectExtent rc=OK
------------{ xstConnectExtent
-------------{ xcsRequestThreadMutexSem
-------------} xcsRequestThreadMutexSem rc=OK
-------------{ xstStorageRequest
--------------{ xstServerRequest
--------------} xstServerRequest rc=OK
-------------} xstStorageRequest rc=OK
-------------{ xcsReleaseThreadMutexSem
-------------} xcsReleaseThreadMutexSem rc=OK
------------} xstConnectExtent rc=OK
-----------} xcsAttachSetExtents rc=OK
----------} xcsAttachSharedSubpool rc=OK
---------} xcsConnectSharedSubpool rc=OK
---------{ xcsGetEnvironmentString
---------} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
---------{ xcsReleaseThreadMutexSem
---------} xcsReleaseThreadMutexSem rc=OK
--------} xcsInitialize rc=OK
--------{ zcpAttachPipe
---------{ xcsConnectSharedMemSet
----------{ xcsRequestThreadMutexSem
----------} xcsRequestThreadMutexSem rc=OK
----------{ xcsRequestThreadMutexSem
----------} xcsRequestThreadMutexSem rc=OK
----------{ xcsReleaseThreadMutexSem
----------} xcsReleaseThreadMutexSem rc=OK
----------{ xstAttachSharedMemSet
-----------{ xstConnectExtent
------------{ xcsRequestThreadMutexSem
------------} xcsRequestThreadMutexSem rc=OK
------------{ xstStorageRequest
-------------{ xstServerRequest
-------------} xstServerRequest rc=OK
------------} xstStorageRequest rc=OK
------------{ xcsReleaseThreadMutexSem
------------} xcsReleaseThreadMutexSem rc=OK
-----------} xstConnectExtent rc=OK
-----------{ xcsGetMem
-----------} xcsGetMem rc=OK
-----------{ xcsGetMem
-----------} xcsGetMem rc=OK
----------} xstAttachSharedMemSet rc=OK
----------{ xcsReleaseThreadMutexSem
----------} xcsReleaseThreadMutexSem rc=OK
---------} xcsConnectSharedMemSet rc=OK
---------{ xllLongLockRequest
----------{ xllAccessMutexHandle
-----------{ xcsReallocMem
-----------} xcsReallocMem rc=OK
-----------{ xcsReallocMem
-----------} xcsReallocMem rc=OK
----------} xllAccessMutexHandle rc=OK
----------{ xcsBuildDumpPtr
-----------{ xcsGetMem
-----------} xcsGetMem rc=OK
----------} xcsBuildDumpPtr rc=OK
----------{ xcsBuildDumpPtr
----------} xcsBuildDumpPtr rc=OK
----------{ xcsFFST |
|
| Back to top |
|
|
| JT |
| Posted: Thu Dec 01, 2005 9:00 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
| Steffi |
| Posted: Fri Dec 02, 2005 2:32 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2005
Posts: 5
|
Hi,
thank you for the hint JT.
I just installed the Refresh Pack, but unfortunately it does not really solve the problem.
After I had let the creation of a queue manager run the last night, it managed to create the new queue manager (although the described error was posted serveral times in the event log).
But nevertheless, the MQ installation cannot be correct, because usually the creation process takes only a few seconds....
Furthermore, I try to set up WebSphere MQ 6.0 on an active/passive cluster with two nodes using Microsoft Clustering Services.
The node on which I created the queue manager first managed to take the corresponding resource online and offline via the Cluster Administrator. But when I tried to bring the resource online on the other node, the processor load there increased to 100 % and it failed with the error already posted.
Sometimes even the clustering services crash because of this problem and initiate a failover...
Does anybody know what causes these problems or whatelse I could try? |
|
| Back to top |
|
|
| sradiraju |
| Posted: Fri Dec 02, 2005 8:32 am Post subject: |
|
|
Apprentice
Joined: 08 Sep 2002
Posts: 34
Location: Chicago,IL
|
Hi Steffi,
Looks like more of an access issue. Can you check if the user-id, you are trying to create Queue Manager, is in mqm group and if not try adding it. Then reboot the machine, windows right, and let us know what happens.
Thanks,
Somesh |
|
| Back to top |
|
|
| Steffi |
| Posted: Mon Dec 05, 2005 6:26 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2005
Posts: 5
|
Hi Somesh,
thank you for your reply.
The user under which MQSeries is running is a special domain user account created according to the installation instructions.
It is already a member of the domain group "domain mqm" and the local group "mqm".
The behaviour of the current MQSeries 6.0 installation is very strange. Even on the cluster node where I can start the Queue Manager, the CPU usage afterwards increases to 100%.
I have already installed MQSeries 5.3 on a MSCS Cluster before, everything worked fine.
I don't know what is different in version 6.0 that could cause such problems. |
|
| Back to top |
|
|
| hguapluas |
| Posted: Wed Dec 14, 2005 2:52 pm Post subject: |
|
|
Centurion
Joined: 05 Aug 2004
Posts: 105
Location: San Diego
|
Have you tried installing on a non-clustered server and replicating your queue creation process to see if it occurs on that server too? If so, then you can more appropriately focus on MQ6 as a cause in the problem. But since you are in a clustered environment, have you checked the communications between clustered servers to be sure that between the clustered servers, all is ok. Sometimes, errors can appear to be app/service related but are triggered as a result of network infrastructure or server configuration issues.
Just a thought. |
|
| Back to top |
|
|
| Steffi |
| Posted: Mon Dec 19, 2005 7:23 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2005
Posts: 5
|
Hi,
thank you for your reply.
Yes, I have tried to install MQSeries 6.0 on a virtual pc with Windows Server 2003. The creation of a queue manager takes only a few seconds in that environment, but a default channel is not created automatically.
Is that right or should the channel be created automatically?
I don't think the problems with version 6.0 occur because of the cluster, because an installation of MQSeries 5.3 on the same cluster works fine. |
|
| Back to top |
|
|
|
|
