ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Q Manager hangs. need to kill a process to reboot

Post new topic  Reply to topic
 Q Manager hangs. need to kill a process to reboot « View previous topic :: View next topic » 
Author Message
vingem
PostPosted: Mon Oct 11, 2004 10:27 am    Post subject: Q Manager hangs. need to kill a process to reboot Reply with quote

Newbie

Joined: 11 Oct 2004
Posts: 2

before applying CSD07 this problem used to happen almost daily around
7.00PM - 8.00pm. after applying CSD07 this has been happening randomly though not often(daily).
below is the fdc reoprt and the error logs can someone please help me find out what the problem is, why this is happening and any ways to rectify this issue ? thanks in advance !.


----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun October 10 22:15:53 Eastern Daylight Time 2004 |
| Host Name :- MQS01 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AL036002 |
| Application Name :- MQM |
| Component :- alsRecordCheckPoint |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- E:\MQSeries53\IBM\WebSphere MQ\bin\amqzllp0.exe |
| Process :- 00001892 |
| Thread :- 00000001 |
| QueueManager :- QMMFD01 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (CreateFile()) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 32 20 |
| Comment1 :- CreateFile() |
| |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zllpMain
alsCheckPointLoop
aocPerformCheckpoint
almEndCheckPoint
alsRecordCheckPoint
xcsFFST

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun October 10 22:15:54 Eastern Daylight Time 2004 |
| Host Name :- MQS01 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005020 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- E:\MQSeries53\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00001688 |
| Thread :- 00000001 |
| QueueManager :- QMMFD01 |
| Major Errorcode :- zrcX_PROCESS_MISSING |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5008 |
| Probe Severity :- 2 |
| Probe Description :- AMQ5008: An essential WebSphere MQ process 1892 cannot |
| be found and is assumed to be terminated. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1892 764 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zxcProcessChildren
xcsFFST


0/10/2004 22:15:53
AMQ6119: An internal WebSphere MQ error has occurred (CreateFile())

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 : 628 --------------------------------------------------------
10/10/2004 22:15:53
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QMMFD01.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1892.
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 : 662 --------------------------------------------------------
10/10/2004 22:15:53
AMQ6118: An internal WebSphere MQ error has occurred (20007002)

EXPLANATION:
An error has been detected, and 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 : 628 --------------------------------------------------------
10/10/2004 22:15:53
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QMMFD01.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1892.
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 : 662 --------------------------------------------------------
10/10/2004 22:15:53
AMQ6125: An internal WebSphere MQ error has occurred.

EXPLANATION:
An internal error has occurred with identifier 0. This message is issued in
association with other messages.
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 : 628 --------------------------------------------------------
10/10/2004 22:15:53
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QMMFD01.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1892.
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 : 662 --------------------------------------------------------
10/10/2004 22:15:54
AMQ5008: An essential WebSphere MQ process 1892 cannot be found and is assumed
to be terminated.

EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
----- amqxfdcp.c : 628 --------------------------------------------------------
10/10/2004 22:15:54
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QMMFD01.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1688.
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 : 662 --------------------------------------------------------
10/10/2004 22:15:54
AMQ5008: An essential WebSphere MQ process 1892 cannot be found and is assumed
to be terminated.

EXPLANATION:
1) A user has inadvertently terminated the process. 2) The system is low on
resources. Some operating systems terminate processes to free resources. If
your system is low on resources, it is possible it has terminated the process
so that a new process can be created.
ACTION:
WebSphere MQ will stop all MQ processes. Inform your systems administrator.
When the problem is rectified WebSphere MQ can be restarted.
Back to top
View user's profile Send private message
siliconfish
PostPosted: Mon Oct 11, 2004 10:52 am    Post subject: Reply with quote

Master

Joined: 12 Aug 2002
Posts: 203
Location: USA

Looks like this is a resource issue, as the amqzllp0.exe is a checkpoint process and its failing while createFile(). Check the available free space on your system.
_________________
siliconfish
Back to top
View user's profile Send private message
JT
PostPosted: Mon Oct 11, 2004 11:01 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

http://www-1.ibm.com/support/docview.wss?uid=swg21029536
Back to top
View user's profile Send private message
Manikandan
PostPosted: Mon Oct 11, 2004 11:24 pm    Post subject: Reply with quote

Voyager

Joined: 07 Jul 2004
Posts: 78

What is the config of the machine.What is the memory size of the machine
Back to top
View user's profile Send private message
JasonE
PostPosted: Tue Oct 12, 2004 1:22 am    Post subject: Reply with quote

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

CreateFile is failing with rc 32 (Arith1 :- 32), which is ERROR_SHARING_VIOLATION, in function alsRecordCheckPoint, probe 2 (last 3 digits of the probeid).

This equates to a failure from the o/s issuing createfile to open the file amqalchk.fil in read/write mode.

Are you sure this particular fdc comes out at the shutdown time, or before/after?
Back to top
View user's profile Send private message
vingem
PostPosted: Tue Oct 12, 2004 7:47 am    Post subject: Reply with quote

Newbie

Joined: 11 Oct 2004
Posts: 2

Manikandan : this is a Windows 2000 Build with a SP 4
the box has more than 30G of free space on the drive where MQ is installed.

JasonE, i think this FDC comes after the Q Manager hangs. but i am not sure if it comes after the reboot or before the reboot(After killing the PID)
our company has forwarded the link that JT provided regarding a backup process or a virus scanner that could be running accessing the file, to our clients, asking them to check if there is really any program running during the same time.
the same error happened yesterday too. and it happened between 7:00 - 8:00pm.
i will follow up and update you guys once i get a response from our clients.
thanks for all your replies so far.atleast we have something to look at to see if thats a problem or not .
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Q Manager hangs. need to kill a process to reboot
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.