| Author |
Message
|
| woolmerc |
 Posted: Wed Aug 11, 2004 9:37 pm Post subject: Windows shutdown errors |
 |
|
Novice
Joined: 12 May 2004
Posts: 21
|
Hi guys,
I have suddenly started to get a whole heap of 'NT event log' errors when I am shutting down Windows. They are all BIPv500 errors. When I examine them more closely they're errors produced from the execution group, the broker and the configuration manager.
The main 2 errors I get are MQ connection and MQBACK errors. Obviously they are the cause of the MQ service shutting down before the broker tries to issue these final commands.
Does anyone know how I can get rid of these and shutdown the broker cleanly?
Here is an example of one of the error messages:
( ConfigMgr ) WebSphere Business Integration queue manager SYSTEM.BROKER.ADMIN.REPLY no longer available.
The Configuration Manager's connections to WebSphere Business Integration queue manager SYSTEM.BROKER.ADMIN.REPLY, and its associated listener, have been lost. This is expected to be a transient situation and the Configuration Manager will stop then restart after a short interval.
Thanks,
_________________
Chris Woolmer
Programmer
KAZ Group Limited |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Fri Aug 13, 2004 11:05 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
You should look at the administration guide.
When you shutdown you should be ending things in certain orders.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Aug 13, 2004 10:11 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You can try shutting down service in following order,
1) USername server and Broker
2) Config Manager
3) Websphere MQ
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| woolmerc |
| Posted: Sun Aug 15, 2004 3:57 pm Post subject: |
|
|
Novice
Joined: 12 May 2004
Posts: 21
|
Yep, definetely agree Kirani - that shutting down these services manually before shutting down Windows will solve my problems.
But isn't this a little annoying? I have never worked with an application where you have to manually shut down services before shutting down Windows.
Does anyone know of some automatic way of getting around this? Do others find they get the same problems as me?
_________________
Chris Woolmer
Programmer
KAZ Group Limited |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Aug 17, 2004 1:58 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
This is a defect. Please raise a PMR.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Aug 17, 2004 8:01 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Chris, what CSD are you running?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| woolmerc |
| Posted: Sun Aug 29, 2004 7:47 pm Post subject: |
|
|
Novice
Joined: 12 May 2004
Posts: 21
|
CSD 3.0 on version 5.0.
I have raised a PMR and IBM have confirmed that it is a known defect.
_________________
Chris Woolmer
Programmer
KAZ Group Limited |
|
| Back to top |
|
|
| moorej_gl |
| Posted: Fri Jul 29, 2005 6:53 am Post subject: |
|
|
Apprentice
Joined: 01 Dec 2003
Posts: 35
Location: Madison, WI
|
| Quote: |
You can try shutting down service in following order,
1) USername server and Broker
2) Config Manager
3) Websphere MQ |
Is this documented anywhere? We're migrating to use MSCS clustering, & I can't seem to find specific recommendations on this. But I do see different behavior when shutting down the config manager before the broker, so am leaning towards creating a dependency for shutdown & startup. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 29, 2005 7:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Certainly don't shut MQ down until all services using it have stopped.
It would seem logical that there would be some dependancies between the broker and the configmgr...
But I'd expect that the configmgr could be kept shut down except when needed... (not that I've tried this, mind you).
I seem to recall a lot more information on broker in a clustered environment in the 2.1 System Administration guide... it's worth a look.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| moorej_gl |
| Posted: Fri Jul 29, 2005 7:13 am Post subject: |
|
|
Apprentice
Joined: 01 Dec 2003
Posts: 35
Location: Madison, WI
|
I can't find much on clustering in the 2.1 guide, but it certainly seems consistent with the v5 documentation in stating that the config mgr runs independently of the broker. But I see no statement saying that the broker does / does not have any dependencies on the config mgr. It obviously depends on the config mgr for deployment of code, but what about everyday operation? Perhaps it's time to give support a call  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 29, 2005 7:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe it was the Installation guide... ?
But yes, open a PMR specifically requesting a complete startup/shutdown procedure for a hardware clustered broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
