| Author |
Message
|
| sudhaRam |
 Posted: Fri Nov 30, 2007 4:19 am Post subject: Queue Manager Ended abnormally |
 |
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
Hi,
Im using MQ V5.3 in HP-UX machine. Suddenly the Queue Manager ended unexpextedly. When trying to start it its not getting started. When checking the MQ error log it says serious error has occured to the Queue Manager. Please help to start the Queue Manager |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Nov 30, 2007 4:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What is the error associated with the queue manager ending unexpectedly? There is most likely an FDC associated with it, the probe id in that will give you additional information.
What happens when you try and start it? What's the error in the log associated with that?
If I had to guess (and I'm only guessing) I'd say the old queue manager didn't end all it's processes and/or release some system resources and this is preventing the new instance.
What CSD is it on?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 4:33 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
Error Message:
When i see the error log /var/mqm/errors it says
An error has been detected and the Websphere MQ error recording routine has been called. The failing process is 17668.
The process keeps on changing timely.
When starting using strmqm Queue Manager Name it says
Log not available.
But the dspmq still shows the Queue Manager has ended unexpectedly
These are the errors we are getting. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 30, 2007 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Are you working with this guy? Or it is a freaky coincidence? 
http://www.mqseries.net/phpBB2/viewtopic.php?t=40814
If the error recording has been called then there will be an FDC because that's what it writes. Get the probe id as I suggested before, it will provide useful information.
And you still have not said what CSD you're on.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 4:56 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
Yes i work with him 
Probe ID please explain im not aware.
The CSD level is CSD04 |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Nov 30, 2007 4:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| sudhaRam wrote: |
Yes i work with him
Probe ID please explain im not aware.
The CSD level is CSD04 |
Go look in the FDC file and put the top of it here.
If you are running v5.3, you are out of support (and I have no idea how old CSD4 is). You should consider moving up to v6. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 5:05 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
The Probe ID is ZX000001
Probe Type: MSGAMQ6118
Probe Descritption: AMQ6118: An internal Websphere MQ error has occured.(7017)
Probe Severity:2 |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 30, 2007 5:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sudhaRam wrote: |
| Yes i work with him |
Then why are you both posting??? 
| sudhaRam wrote: |
| Probe ID please explain im not aware. |
Now you've found it, you look it up. And get this:
http://www-1.ibm.com/support/docview.wss?uid=swg21179695
| sudhaRam wrote: |
| The CSD level is CSD04 |
That's very, very, very old. Upgrade. Now. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 5:27 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
He has stopped psoting.
Thanks i will look into the link. Also we are wiaitng for the approval from the management to upgrade the version and CSD |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 30, 2007 5:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sudhaRam wrote: |
| . Also we are wiaitng for the approval from the management to upgrade the version and CSD |
At least move to a more recent CSD of v5.3 until the upgrade to v6 is approved!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 6:41 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
| Thanks for ur help. The Queue Manager is running now. But now we r facing another issue here. This UNIX Queue manager communicates with mainframe. While the UNIX queue manager was ended lots of messages accumulated in the transmission Queue. Now we started the UNIX channels. The Sender Channels in the Mainframe are not starting. It is retrying. Do we have to empty the Transmission Queue and try? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 30, 2007 6:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sudhaRam wrote: |
| Do we have to empty the Transmission Queue and try? |
NO!!!!!!!!!!!!!!!!!!!!!
If the sender channels on the m/f are retrying, they can't establish connection with the receivers on Unix. Clearing the xmitq will not change that, aside from annoying all the people who's messages you've just deleted.
Work out (with the aid of the logs) what the problem with the receivers is. I'd start by checking the listener.
And read the System Admin manual!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sudhaRam |
| Posted: Fri Nov 30, 2007 6:49 am Post subject: |
|
|
Novice
Joined: 13 Nov 2007
Posts: 12
|
| yes we also checked the Listener. Its up and running. Also the receivers are not stopped in the UNIX end. anyways we r finding out |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Nov 30, 2007 7:37 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3253
Location: London, ON Canada
|
Hi,
What error messages are in the general mq error log and queue manager error log? Do you see anything about unresolved transactions or channel sequence number problem?
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Nov 30, 2007 8:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
and what did you do to get the QM running, since that can give us a clue as to why your channels are retrying. (Like Roger said, the logs probably give a big clue)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
