| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Qmgr ended preemitively |
« View previous topic :: View next topic » |
| Author |
Message
|
| srikanthmq225 |
 Posted: Thu Jan 02, 2014 3:01 am Post subject: Qmgr ended preemitively |
 |
|
Novice
Joined: 15 Oct 2013
Posts: 21
|
Hi,
We are using MQ 7.5.0.1 in windows server 2008
problem is i taken the qmgr backup using 'saveqmgr' support pack (ms03_win).
After take the backup... qmgr status is 'ended preemitively'.
I didnt understand why it was happened...
Still the qmgr is in Ended preemitively..
we are using MSCS clusters(two nodes)... the above happend in 1st node(Server)...so i transfered all qmgrs to 2nd node . Then that qmgr is working(running) fine...
but in 1st node(server), its not running...
please help me...how to solve this issue..
I mentioned all QMGR errors and System errors and FDC file also...
Queue Manager errors:
| Quote: |
--------------------------
12/23/2013 09:17:17 - Process(10436.1) User(f_wmq_qa) Program(amqzmgr0.exe)
Host(ST-W4002) Installation(WMQ75)
VRMF(7.5.0.1) QMgr(Q0204)
AMQ5023: The channel initiator has ended. ProcessId(5276).
EXPLANATION:
The channel initiator process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
12/23/2013 09:17:20 - Process(6164.5) User(f_wmq_qa) Program(runmqlsr.exe)
Host(ST-W4002) Installation(WMQ75)
VRMF(7.5.0.1) QMgr(Q0204)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'Q0204' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- cmqxrmsa.c : 417 --------------------------------------------------------
12/23/2013 09:17:20 - Process(10436.1) User(f_wmq_qa) Program(amqzmgr0.exe)
Host(ST-W4002) Installation(WMQ75)
VRMF(7.5.0.1) QMgr(Q0204)
AMQ5027: The listener 'LIST.TCP' has ended. ProcessId(6164).
EXPLANATION:
The listener process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
12/23/2013 09:17:25 - Process(10436.1) User(f_wmq_qa) Program(amqzmgr0.exe)
Host(ST-W4002) Installation(WMQ75)
VRMF(7.5.0.1) QMgr(Q0204)
AMQ5025: The command server has ended. ProcessId(11612).
EXPLANATION:
The command server process has ended.
ACTION:
None.
System Errors:
----------------
12/23/2013 09:37:25 - Process(916.394) User(f_biztalk_wmq7) Program(dllhost.exe)
Host(ST-W4003) Installation(WMQ75)
VRMF(7.5.0.1)
AMQ6118: An internal WebSphere MQ error has occurred (2E)
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 any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 867 --------------------------------------------------------
12/23/2013 09:37:25 - Process(916.394) User(f_biztalk_wmq7) Program(dllhost.exe)
Host(ST-W4003) Installation(WMQ75)
VRMF(7.5.0.1)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 916.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 912 --------------------------------------------------------
12/23/2013 09:37:28 - Process(916.394) User(f_biztalk_wmq7) Program(dllhost.exe)
Host(ST-W4003) Installation(WMQ75)
VRMF(7.5.0.1)
AMQ6118: An internal WebSphere MQ error has occurred (2E)
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 any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 867 --------------------------------------------------------
12/23/2013 09:37:28 - Process(916.394) User(f_biztalk_wmq7) Program(dllhost.exe)
Host(ST-W4003) Installation(WMQ75)
VRMF(7.5.0.1)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 916.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 912 --------------------------------------------------------
|
FDC file:
---------
| Quote: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon December 23 2013 09:37:25 W. Europe Standard Time |
| UTC Time :- 1387787845.475000 |
| UTC Time Offset :- 60 (W. Europe Standard Time) |
| Host Name :- ST-W4003 |
| Operating System :- Windows Server 2008 R2 Server Enterprise Edition, |
| Build 7601: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.5.0.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- C:\IBM\WMQ |
| Installation Name :- WMQ75 (1) |
| Probe Id :- UN103000 |
| Application Name :- MQM |
| Component :- MQResourceDisp::DestroyResource |
| SCCS Info :- ~%x, |
| Line Number :- 797 |
| Build Date :- Mar 8 2013 |
| Build Level :- p750-001-130308 |
| Build Type :- IKAP - (Production) |
| UserID :- f_biztalk_wmq7 |
| Process Name :- C:\Windows\SysWOW64\dllhost.exe |
| Addressing mode :- 32-bit |
| Process :- 00000916 |
| Thread :- 00000394 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- Unknown(2E) |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (2E) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 46 2e |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon December 23 2013 09:37:28 W. Europe Standard Time |
| UTC Time :- 1387787848.502000 |
| UTC Time Offset :- 60 (W. Europe Standard Time) |
| Host Name :- ST-W4003 |
| Operating System :- Windows Server 2008 R2 Server Enterprise Edition, |
| Build 7601: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.5.0.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- C:\IBM\WMQ |
| Installation Name :- WMQ75 (1) |
| Probe Id :- UN103000 |
| Application Name :- MQM |
| Component :- MQResourceDisp::DestroyResource |
| SCCS Info :- ~%x, |
| Line Number :- 797 |
| Build Date :- Mar 8 2013 |
| Build Level :- p750-001-130308 |
| Build Type :- IKAP - (Production) |
| UserID :- f_biztalk_wmq7 |
| Process Name :- C:\Windows\SysWOW64\dllhost.exe |
| Addressing mode :- 32-bit |
| Process :- 00000916 |
| Thread :- 00000394 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- Unknown(2E) |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (2E) |
| FDCSequenceNumber :- 1 |
| Arith1 :- 46 2e |
| |
+-----------------------------------------------------------------------------+
|
EDIT by exerk: stack trace removed as it's only of use to IBM Support, and log/FDC entries rendered easier to pick out. |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Jan 02, 2014 3:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Google gave me a hit first time for the Probe Id, admittedly at V6.0 but giving MSDTC a mention, and as you're using BizTalk presumably you have configured the DTC for High Availability?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jan 02, 2014 4:15 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Why are you not using the builtin command for backing up the configuration of a V7.5 queue manager?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jan 02, 2014 4:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| smdavies99 wrote: |
| Why are you not using the builtin command for backing up the configuration of a V7.5 queue manager? |
Possibly because it can't be guaranteed to back up everything? 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| srikanthmq225 |
| Posted: Thu Jan 02, 2014 5:37 am Post subject: |
|
|
Novice
Joined: 15 Oct 2013
Posts: 21
|
Hi exerk,
thank you for your reply..
i didn't understand what you said...
"admittedly at V6.0 but giving MSDTC a mention, and as you're using BizTalk presumably you have configured the DTC for High Availability? "
becasue I'm new to my environment...
please explain detailly...
thank you.. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jan 02, 2014 6:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The Probe Id gave THIS HIT, which indicated a problem with the Microsoft Distributed Transaction Coordinator (MSDTC) at WebSphere MQ Version 6.0. You may, or may not, be encountering the same problem at the WebSphere MQ version you are using, perhaps only raising an IBM Problem Management Record (PMR) may tell
It could also be something as simple as a configuration problem. As you are using a Microsoft Cluster Server (MSCS) environment I am speculating that you have made your queue manager an MSCS resource? If so, consider what other resources may also have to be Highly Available
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| 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
|
|
|
|
