Has anyone noticed problems with MQ 6.0.2.1 on Windows that seem related
to memory? The following two scenarios I would see every once in a great
while at MQ 5.3, but they seem more common ever since I upgraded to
6.0.2.1.

The Windows 2000 servers are old, obviously, and have a couple of gig of
memory. They will be replaced soon. The WIN2K3 server have 8-12 GB of
memory and are 2-3 years old.


Scenario 1
I stop the QM for whatever reason. More often than not if I try and
restart the QM it complains about previously running processes having
some sort of hook into MQ. This was never a problem in MQ 5.3. Constant
problem in MQ 6.0.2.1. Happens in both WIN2K and WIN2K3. Usually this is
the QPASA monitoring agent or the BizTalk MQS Agent (dllhost.exe).
Sometimes it's a command server or channel initiator.

----- amqxfdcp.c : 810
--------------------------------------------------------
10/19/2007 06:56:26 - Process(1240.2) User(ID_I_have_MQ_running_under)
Program(amqmsrvn.exe)
AMQ7880: Error code 24 starting MYMQ/Queue Manager WebSphere MQ service.

EXPLANATION:
The service was unable to start MYQM/Queue Manager. The error message
reported was as follows: AMQ8041: The queue manager cannot be restarted
or
deleted because processes, that were previously connected, are still
running.
Process 4240 is still running. AMQ7018: The queue manager operation
cannot be
completed.
ACTION:
Use WebSphere MQ Explorer to investigate why the service could not
begin. If
recovery for this service is active, MQ will attempt to recover. 
------------------------------------------------------------------------
-------


Scenario 2
An amqrmppa process goes bad. It start writing to an FDC over and over.
The QM and system MQ error logs get the below error over and over. I can
get out of this by killing the PID that corresponds to the amqrmppa
process. Obviously those channels using that amqrmppa process get
whacked, but all others and the QM remain fine. The channels that got
whacked reconnect via the other existing amqrmppa processes, or the
listener spawns a new one if needed. I see this only on the Windows 2000
servers. Maybe once every couple weeks, whereas before the MQ 6.0
upgrade it would happen once a year if that.

Task Manager says there is plenty of memory available while this is
happening.

10/19/2007 06:55:57 - Process(5104.28402) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 268460419.
----- amqxfdcp.c : 810
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28402) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 536895769.
----- amqxfdcp.c : 766
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28402) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 268460419.
----- amqxfdcp.c : 810
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28403) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 536895769.
----- amqxfdcp.c : 766
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28403) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 268460419.
----- amqxfdcp.c : 810
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28403) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 536895769.
----- amqxfdcp.c : 766
--------------------------------------------------------
10/19/2007 06:55:57 - Process(5104.28403) User(mqadmin_ad1)
Program(amqrmppa.exe)
AMQ6090: MQM could not display the text for error 268460419.


And the FDC gets this over and over, getting HUGE until we kill the PID:
+-----------------------------------------------------------------------
------+
|
|
| WebSphere MQ First Failure Symptom Report
|
| =========================================
|
|
|
| Date/Time         :- Fri October 19 06:49:54 Eastern Daylight Time
2007     |
| Host Name         :- MyServernName(Windows 2000, Build 2195: Service
Pack 4)|
| PIDS              :- 5724H7200
|
| LVLS              :- 6.0.2.1
|
| Product Long Name :- WebSphere MQ for Windows
|
| Vendor            :- IBM
|
| Probe Id          :- XY129005
|
| Application Name  :- MQM
|
| Component         :- xstConnectExtent
|
| SCCS Info         :- lib/cs/pc/winnt/amqxsten.c, 1.45.1.5
|
| Line Number       :- 1013
|
| Build Date        :- Mar 26 2007
|
| CMVC level        :- p600-201-070323
|
| Build Type        :- IKAP - (Production)
|
| UserID            :- mqadmin_ad1
|
| Process Name      :- E:\Programs\MQSeries\bin\amqrmppa.exe
|
| Addressing mode   :- 32-bit
|
| Process           :- 00005104
|
| Thread            :- 00028192
|
| ConnId(4) App     :- 0
|
| Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
|
| Minor Errorcode   :- OK
|
| Probe Type        :- MSGAMQ6119
|
| Probe Severity    :- 2
|
| Probe Description :- AMQ6090: MQM could not display the text for error
|
|   536895769.
|
| FDCSequenceNumber :- 34102
|
| Arith1            :- 536895769 20006119
|
| Arith2            :- 8 8
|
| Comment1          :- Failed to attach shared memory map:
Handle(0002BE28)   |
|   [rc=536895
|
| Comment2          :- Not enough storage is available to process this
|
|   command.
|
|
|
+-----------------------------------------------------------------------
------+
 
Peter Potkay
MQSeries Team Leader
IBM Global Services - The Hartford Account
Hartford email: [EMAIL PROTECTED]
IBM email: [EMAIL PROTECTED] 
Office Phone: 1-860-547-7906
Cell Phone: 1-860-202-1375
Pager: 1-800-203-3375



*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************


To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Reply via email to