| Author |
Message
|
| Ramphart |
 Posted: Mon Sep 20, 2004 2:11 am Post subject: WMQI 2.1 Broker, Control Centre problem - Urgent pls |
 |
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
Hi,
- I'm using WMQI 2.1 CSD 07 on Windows 2000.
- I'm getting the following errors in my event log when I start the config manager and broker on my machine:
ERROR 1
Description:
( BRK_PROTO.WMS ) Database record associated with message flow '4ba692bf-fe00-0000-0080-f5da7178c8af' is not valid.
The message broker found a database record associated with the persistent state of message flow '4ba692bf-fe00-0000-0080-f5da7178c8af' to be invalid. The active broker state may not be as expected.
See the following message or messages for details of the error. Attempt to correct the error or errors by redeploying the complete broker configuration from the Control Center. If the problem persists, contact your IBM support center.
ERROR 2
Description:
( BRK_PROTO.WMS ) XML Parsing Errors have occurred.
Errors have occurred during parsing of XML.
Review further error messages for an indication to the cause of the errors.
ERROR 3
Description:
( BRK_PROTO.WMS ) XML parsing error (The attribute 'label' is already used in element 'ComIbmDebugNode') encountered on line 146 column 462 while parsing element MessageFlow.
The above error was reported by the generic XML parser.
This message is usually caused by a badly-formed XML message. Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. Note that the line number and column number quoted above give the position where the parser discovered the problem. The actual error may be earlier in the message. Internal error codes : (84), ().
HELP HELP HELP
-I cannot open my Control Center to redeploy the entire config on the broker.
-Does anybody know how the broker got itself in this state and how I can fix this?
_________________
Applications Architect |
|
| Back to top |
|
 |
| Missam |
| Posted: Mon Sep 20, 2004 6:54 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
| It looks like your broker got screwed up and its not starting up.Is there any SQL errors reported along with these errors ?.try redefining your odbc data source.if this doesn't work you may need to recreate your broker.Is it a production box or development play ground..? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 20, 2004 6:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The startup of the broker, and the config manager should be unrelated.
That is, even if the broker doesn't start, you should be able to open the control center.
If you can't, then the configuration manager isn't starting.
I've seen the same errors you are showing on 2.1 brokers when I had to force a broker to stop because of a message flow loop. But the incidence of the errors didn't affect the broker functionality.
Try this: Stop the broker, stop the config manager. Start ONLY the config manager.
What is reported in the logs, then?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ramphart |
| Posted: Mon Sep 20, 2004 10:48 am Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
I've tried EVERYTHING - In the end I reinstalled the software. Dunno why the broker got itself screwed 
_________________
Applications Architect |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Sep 20, 2004 2:44 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
I don't remember correctly but I'd got a similar error messages so one year ago caused by a special character in message flow description (it was a hungarian letter Ű  it is a U with double acute).
After restoring nightly backup of database it worked without problem. Alternative solution is a database hacking - deleting by UUID, slightly dangerous when you cause inconsistency...
Tibor |
|
| Back to top |
|
|
| Missam |
| Posted: Tue Sep 21, 2004 6:01 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
Reinstalling the software doesn't solve your problem,because it won't delete and recreate your broker ,your broker will remain same in this operation.
what do you mean by you tried EVERY THING...? |
|
| Back to top |
|
|
| Ramphart |
| Posted: Tue Sep 21, 2004 10:05 pm Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
Reinstalling the software and recreating the broker soleved this issue for some reson. Before I reinstalled the software the CC would not open. It merely showed as a minimized icon and there were no error messages anaywhere. Anyway, all working good now.
_________________
Applications Architect |
|
| Back to top |
|
|
|
|
