| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Stack dump when deploying debug flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| jgooch |
 Posted: Thu Mar 20, 2003 8:01 am Post subject: Stack dump when deploying debug flow |
 |
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
We deployed a flow through the Control Centre debugger and it seems to have corrupted the broker. We now get BIP1536S errors when trying to deploy to the broker. Furthermore, the execution group is throwing stack dump files out every few seconds and reporting the following error to the syslog:-
| Quote: |
| Mar 20 16:35:17 localhost WMQIv210[4853]: [ID 000000 user.error] (BSOLD01.NEWMONEY)[1]BIP2228E: Severe error: /build/S210_P/src/CommonServices/Unix/ImbAbend.cpp 417 signal received Abend file: /var/wmqi/errors/BSOLD01.NEWMONEY.4853.1.abend action: abort |
We have tried to deploy the broker without the debug flow but to no avail. We've bounced MQSI and DB2 and MQ without luck. We haven't deleted the broker yet because we are concerned that the config mgr will get out of line and we will not be able to recreate it (this has happened before).
We're running v2.1 on MQ5.3 on Solaris 8.
Does anyone have any ideas how to recover the situation? Any clues as to what caused it?
Thanks,
J. |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Mar 21, 2003 4:54 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Have you tried doing a complete deploy of the broker?
If it fails to do a complete deploy then REMOVE (not delete) all message flows from your Broker/Execution Groups and then try to do a complete deploy of the broker.
_________________
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 |
|
|
| jgooch |
| Posted: Mon Mar 24, 2003 1:53 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
Kiran,
We've tried complete deploys, with and without the debug flow. We've also tried forced deploys.
This morning, I've tried it again and I get the errors:-
| Quote: |
| BIP1536S: Configuration Manager unable to register for internal subscriptions with broker BSOLD01. |
...and...
| Quote: |
| BIP2066E: Broker BSOLD01 (UUID b1046047-f300-0000-0080-81d1297688ac) was unable to retrieve an internal configuration response message for execution group 'NEWMONEY' within the 360 second Configuration Timeout. |
The broker configuration in the assignment tab that I am trying to deploy has only the "default" execution group. There are no flows and no message sets.
(NB NEWMONEY was the name of the group including the debug flow that was the cause of this mess)
I think we'll have to delete and recreate but I am very wary of doing this as we have previously (in v2.0.1) ended up with "ghost" brokers in the config mgr.
What is the safest way to delete the broker, without causing issues in the config mgr (bearing in mind that we cannot get a successful deploy of an empty broker to work)?
Thanks,
J. |
|
| Back to top |
|
|
| jgooch |
| Posted: Tue Mar 25, 2003 6:28 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
Just to close this off:-
We've recovered our system. There's no definitive answer as to what caused the problem, although fingers are pointing at CSD04 having been incorrectly applied.
For reference, a way to ensure a broker is deleted cleanly (ie removed from the config mgr) in cases where the system has got itself in a tizzy is:-
| Quote: |
1. Stop the CC
2. Stop the CM
3. Stop the Broker
4. Delete the Broker physically on the Solaris machine (mqsidelete broker
...)
5. Run the cleanup script below to the CM database (eg. MQSICMDB)
Replace MYCONFIGMGRDB with your ConfigMgr database and
MYBROKER with your
broker name in the script below.
Copy and paste this script into the Script window of your DB2 Command
Center and Execute.
connect to MYCONFIGMGRDB
delete from cbrokerceg where cuuid=(select distinct cuuid from cbroker
where cname='MYBROKER' )
delete from ceg where cbrokercuuid=(select distinct cuuid from cbroker
where cname='MYBROKER' )
delete from coutstanding where cbrokercuuid=(select distinct cuuid from
cbroker where cname='MYBROKER')
delete from cproperties where cbrokercuuid=(select distinct cuuid from
cbroker where cname='MYBROKER')
delete from ctopic where cbrokercuuid=(select distinct cuuid from cbroker
where cname='MYBROKER')
delete from cbroker where cname='MYBROKER'
connect reset
6. Recreate the Broker
7. Start all components
8. Add the new Broker to the Topology
9. Deploy that change to the CM
10. Recreate your Broker domain by adding the EGs, assigning message
flows, etc. |
Thanks to IBM (in Germany) for the clear instructions above. Naturally, they should only be used when the normal broker deletion procedure has failed.
J. |
|
| 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
|
|
|
|
