MQSeries.net :: View topic - Queue manager Not being created... Interesting one...

mqonnet · Posted: Fri Apr 04, 2003 2:58 pm Post subject:

Discovered this problem while i was playing around a bit.

I wrote a "C" program to create and "n" number of queue managers for my testing purposes. It works fine all the time, creating and staring them. But fails always when it reaches 113. Not sure if this is a magic figure or what... :).

As for the error.

Here's an extract from system log

-------------------------------------------------------------------------------
04/04/2003 16:53:11
AMQ6118: An internal MQSeries error has occurred (20806805)

EXPLANATION:
An error has been detected, and the MQSeries 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.
-------------------------------------------------------------------------------
04/04/2003 16:53:11
AMQ6184: An internal MQSeries error has occurred on queue manager QM113.

EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 14840.
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.
-------------------------------------------------------------------------------
04/04/2003 16:53:11
AMQ6118: An internal MQSeries error has occurred (20806716)

EXPLANATION:
An error has been detected, and the MQSeries 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.
=================

I also got an FFST raised alongside which is as below.

+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Fri April 04 16:53:11 Pacific Standard Time 2003 |
| Host Name :- TEST (NT Version 5.0 Build 2195: Service Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- HL000001 |
| Application Name :- MQM |
| Component :- hlgStartLog |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- Fred |
| Process Name :- C:\Program Files\MQSeries\bin\amqzxma0.exe |
| Process :- 00014840 |
| Thread :- 00014848 |
| QueueManager :- QM113 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_MQLO_SEMA |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred |
| (20806805) |
| Arith1 :- 545286149 20806805 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
kpiStartup
apiStartup
aocStartDAP
almStartup
alsInitGlobal
hlgStartLog
xcsFFST

MQM Trace History
----------} xstAllocBlockInSharedMemSet rc=OK
---------} xstAllocateMemBlock rc=OK
--------} xcsAllocateMemBlock rc=OK
-------} hosCreateMutexSem rc=OK
-------{ hosCreateMutexSem
--------{ xcsAllocateMemBlock
---------{ xstAllocateMemBlock
----------{ xstAllocBlockInSharedMemSet
-----------{ xstAllocBlockInAnExtentOnList
------------{ xstSerialiseExtentList

***************

Amazingly enough though, the qm, QM113 did not get started. So, i went into the errors directory of this qm to see nothing in there. NO mqerrlog file in it at all. So, which meant that the QM was not properly created at all.

The question are.

1) Why does this happen.
2) Is there any reasoning behind it and how to find out what went wrong. Since there isnt much than the info that i posted here to show.
3) Has anyone else come accross this or is this a known bug.
4) For that matter, has anyone tried something like this and if yes, what was the outcome.

I am still trying to investigate this further, but i doubt would go anywhere.

Platform : Win2k.
MQ rel : V5.2 GA

When i get a chance i shall try and see if i can reproduce this on V5.3, but this is it for now.

Any inputs highly appreciated.

It could be pretty much possible that this is a bug and has been resolved in either CSD's or v5.3, and i am not aware of it.

Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator