| Author |
Message
|
| Meow |
 Posted: Thu Jan 29, 2004 4:41 pm Post subject: Parsing Error |
 |
|
Voyager
Joined: 25 Jun 2003
Posts: 95
|
when i start my broker i see the following errors in my event viewer
Database record associated with message flow 'ef98d243-fa00-0000-0080-a214852c5d5b' is not valid.
The message broker found a database record associated with the persistent state of message flow 'ef98d243-fa00-0000-0080-a214852c5d5b' to be invalid. The active broker state may not be as expected.
Thanks,
meow |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Jan 30, 2004 12:44 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
nothing more?
no BIP messages?
which version / csd / database are you using?
is this a new install or has it been running before?
Michael |
|
| Back to top |
|
|
| Meow |
| Posted: Fri Jan 30, 2004 5:32 am Post subject: |
|
|
Voyager
Joined: 25 Jun 2003
Posts: 95
|
WMQI 2.1/CSD 6/DB2/WIN NT
it is running before.
Please let me know |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jan 30, 2004 7:58 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I have still no clue and my crystal ball is out of order 
Michael |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Jan 31, 2004 7:41 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
ok maybe my crystal ball is not out of order...
I bumped into the same message on my broker, but there is more ... when you scroll down the rest of your message do you also see:
| Quote: |
| 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. |
If yes, what do the following messages say?
Mine are:
| Quote: |
( WMQI.default ) 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. |
| Quote: |
( WMQI.default ) XML parsing error (The attribute 'label' is already used in element 'ComIbmDebugNode') encountered on line 8 column 1073 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), (). |
| Quote: |
| Check the MQSeries completion and reason codes in the MQSeries Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If the open failed because the queue manager or queue did not exist, define these objects to MQSeries. If the failure of the open was because incorrect object names were specified, correct the message flow configuration and attempt to redeploy the message broker. |
Let us know 
Michael |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Feb 01, 2004 2:34 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
This can be caused by a debug process.
Just do a full deploy of your broker, this will sort things out.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
|
|
