| Author |
Message
|
| pfaulkner |
 Posted: Tue Apr 09, 2002 3:29 pm Post subject: |
 |
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Anyone know what would cause me to get these errors from my Broker....
Apr 9 17:19:46 cose2e1 WMQIv210[45048]: (BROKER1.my execution group)[1]BIP5009E: XML Parsing Errors have occurred. : BROKER1.e
20c2798-ec00-0000-0080-ef8ed9a98840: /build/S000_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 355: ImbXmlParser::parseRightSibling: :
Apr 9 17:19:46 cose2e1 WMQIv210[45048]: (BROKER1.my execution group)[1]BIP5004E: An error has been reported by the BIPXML4C component: code '84'; public id ''; line number '11'; column number '2007'; current element 'MessageFlow'; error text 'The attribute 'label' is already used in element 'ComIbmDebugNode''. : BROKER1.e20c2798-ec00-0000-0080-ef8ed9a98840: /build/S000_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.cpp: 677: XmlBrokerAsgardParser::error: :
Apr 9 17:19:49 cose2e1 WMQIv210[45048]: (BROKER1.my execution group)[4113]BIP4283E: A connection error occurred. : BROKER1.e20c2798-ec00-0000-0080-ef8ed9a98840: /build/S000_P/src/Vdb/ImbDebugNode.c: 263: VDB_ConnectToController: :
Apr 9 17:21:11 cose2e1 WMQIv210[30714]: (BROKER1)[1]BIP2080E: Execution Group JavaPlugin failed to return an internal configuration Start message response within a 60 second time period. : BROKER1.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 5630: ImbAdminAgent::getXMLResponse: :
Apr 9 17:21:11 cose2e1 WMQIv210[30714]: (BROKER1)[1]BIP2080E: Execution Group default failed to return an internal configuration Start message response within a 60 second time period. : BROKER1.agent: /build/S000_P/src/AdminAgent/ImbAdminAgent.cpp: 5630
: ImbAdminAgent::getXMLResponse: :
Apr 9 17:21:11 cose2e1 WMQIv210[30714]: (BROKER1)[1]BIP2080E: Execution Group my execution group failed to return an internal
configuration Start message response within a 60 second time period. : BROKER1.agent: /build/S000_P/src/AdminAgent/ImbAdminAgen
t.cpp: 5630: ImbAdminAgent::getXMLResponse: :
_________________
Paul Faulkner |
|
| Back to top |
|
 |
| kolban |
| Posted: Tue Apr 09, 2002 6:58 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| It sounds like a previous debugging session using the Control Center debugger left the message flow in a poor state. Perform a full deploy and see if the problem is rectified. Make sure you have the latest maintenance (CSD 2) applied. |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Wed Apr 10, 2002 6:52 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| We do have CSD2 installed (you installed it). I already tried a full deploy with force. |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Wed Apr 10, 2002 7:52 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
I tried removing all my Execution Groups and created one new empty one. Stopped and restarted the Broker and Config Mgr. Still getting the same errors. A deployment never completes so I always have to use the Complete Force deploy option. Previous to getting these errors I was testing out the debug functions.
_________________
Paul Faulkner |
|
| Back to top |
|
|
| Naftalanja |
| Posted: Wed Apr 10, 2002 11:17 am Post subject: |
|
|
Acolyte
Joined: 30 Jan 2002
Posts: 63
Location: Los Angeles
|
| I had similar kind of problems, i was using the debug mode and after that it created quite a few number of problems. The way i did was, i think it sconfig manager data base or broker database, you should see a table named CBROKER. Open the table and view the sample contents, and please let me know what is the broker status, is it dpled, dpling, gravel etc basing on that i can suggest you the best way. thanks |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Wed Apr 10, 2002 11:34 am Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| I see two enties for my broker (BROKER1), the first has a status of SHARED and the 2nd has DEPLED. |
|
| Back to top |
|
|
| pfaulkner |
| Posted: Wed Apr 10, 2002 12:32 pm Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
Ok, somehow I managed to get past those errors. Don't ask me how!
Now my deploy seems to work because my flows are being used BUT I get these errors...
Apr 10 14:23:24 cose2e1 WMQIv210[47128]: (BROKER1.execution group 1)[3599]BIP4041E: Execution group 'execution group 1' received an invalid configuration message. See the following messages for details of the error. : BROKER1.4287da1d-ed00-0000-0080-ef8ed9a98840: /build/S000_P/src/DataFlowEngine/ImbConfigurationN
ode.cpp: 334: ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
Apr 10 14:23:24 cose2e1 WMQIv210[47128]: (BROKER1.execution group 1)[3599]BIP2230E: Error detected whilst processing a message in node 'DynamicSubscriptionEngine'. : BROKER1.4287da1d-ed00-0000-0080-ef8ed9a98840: /build/S000_P/src/DataFlowEngine/ImbPubSubResource.cpp: 934: ImbPubSubResource::handleResource: DynamicSubscriptionEngine: DynamicSubscriptionEngine
Apr 10 14:23:24 cose2e1 WMQIv210[47128]: (BROKER1.execution group 1)[3599]BIP7150E: User id 'db2admin' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSISVRCFG' using accounting token '0000000000000000000000000000000000000000000000000000000000000000'. : BROKER1.4287da1d-ed00-0000-0080-ef8ed9a98840: /build/S000_P/src/DataFlowEngine/ImbPubSubSubscribeMessageHandler.cpp: 261: ImbPubSubSubscribeMessageHandler::getAttributes: ComIbmPSControl
Node: ControlNode
|
|
| Back to top |
|
|
| kirani |
| Posted: Wed Apr 10, 2002 12:34 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You will always find these two entries for each broker in your domain in CBROKER table. Whenever a deploy operation is pending for a particular broker, you will see third entry with DEPLING.
Whenever I had similar problems, I followed these steps and it always worked for me.
1. Remove all message flows from EG's.
2. Do a complete forced deploy of the broker and wait patiently until the deploy is completed (Check the log messages).
3. Restart the broker once.
4. Start deploying message flows to EGs.
you should keep close watch on messages in the Eventlog/syslog.
Good luck!
_________________
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 |
|
|
| el_pollo_del_mar |
| Posted: Wed Nov 27, 2002 1:41 pm Post subject: |
|
|
Novice
Joined: 01 Jul 2002
Posts: 13
|
I've been having a similar problem.
The event log shows the following message when the broker is first started:
Database record associated with message flow '3155eb94-f100-0000-0080-b9fcd746b028' is not valid.
The message broker found a database record associated with the persistant state of message flow '3155eb94-f100-0000-0080-b9fcd746b028' to be invalid. The active broker state may not be as expected.
I've tried the recommended steps of Forced deployment and restarting, since I believe this message was triggered by a debug session, but it has had no effect. |
|
| Back to top |
|
|
| lillo |
| Posted: Thu Nov 28, 2002 5:45 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
Hi,
I also found that error and it seems a debugger problem when you stop a debugger session in a non-standard way.
| Quote: |
Database record associated with message flow '3155eb94-f100-0000-0080-b9fcd746b028' is not valid.
The message broker found a database record associated with the persistant state of message flow '3155eb94-f100-0000-0080-b9fcd746b028' to be invalid. The active broker state may not be as expected.
|
The error is produced, at least in my case, every time a start the broker. I was talking IBM Support and they gave me this solution.
Make sure you only have one entry with this code in the broker database.
| Code: |
SELECT COUNT(*) FROM BROKERRESOURCES WHERE ResourceName='3155eb94-f100-0000-0080-b9fcd746b028'
|
If this check reveals a count of 1 then to correct the problem connect to your broker database and enter the following command:
| Code: |
DELETE FROM BROKERRESOURCES WHERE ResourceName='3155eb94-f100-0000-0080-b9fcd746b028'
|
Now the problem is gone.
Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| el_pollo_del_mar |
| Posted: Thu Nov 28, 2002 1:09 pm Post subject: |
|
|
Novice
Joined: 01 Jul 2002
Posts: 13
|
| Many thanks, Lillo. That's fixed it! |
|
| Back to top |
|
|
|
|
