| Author |
Message
|
| MQGuy2000 |
 Posted: Thu Dec 18, 2003 12:27 pm Post subject: Error while deploying |
 |
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
Hi Guys,
Help please.
- I created a message flow and deployed it. I tested it with a XML message and I worked fine.
And this is teh esql code when it worked fine.
---
SET OutputRoot = InputRoot;
--
-Now I add teh following line to the esql and after that I cannot deploy my message flow.
OutputRoot.XML.OuterMessage.nweField = 'TEST';
Error Message
--------------
BRKR_2_BROKER_QM1.default ) Execution group 'default' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary plug-ins are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
BRKR_2_BROKER_QM1.default ) Message flow 'MSGFLOW2' could not be reconfigured because it remained busy for longer than the timeout period of '300000'
A request to reconfigure the message flow 'MSGFLOW2' was received but this could not be processed because it remained busy processing a message for longer than the timeout specified.
This can be caused by the timeout being too short considering the complexity of the flow and the size of the messages being processed. In such cases the timeout should be increased. It can also be caused by message flows containing infinite loops. In such cases the SQL should be corrected.
My message:
--------------
<?xml version="1.0" encoding="UTF-8"?>
<OuterMessage>
<field1> 1</field1>
<field2> 1</field2>
<field3> 1</field3>
<field4> 1</field4>
<field5> 1</field5>
</OuterMessage>
Pl. help.
regards |
|
| Back to top |
|
 |
| skn |
| Posted: Thu Dec 18, 2003 12:40 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
-Now I add teh following line to the esql and after that I cannot deploy my message flow.
OutputRoot.XML.OuterMessage.nweField = 'TEST';
Isn't SET missing in the ESQL?
If it aint ,then it looks like the flow has entered an infinite loop.
What domain are you using ? |
|
| Back to top |
|
|
| MQGuy2000 |
| Posted: Thu Dec 18, 2003 12:41 pm Post subject: |
|
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
Infinite loop?
Well thats what the error says too. How does it happen.
I am using XML message domain.
Can u pl. explain little bit about how u thought it went to infinite loop.
ALL and any info is GREATLY appreciated. |
|
| Back to top |
|
|
| MQGuy2000 |
| Posted: Thu Dec 18, 2003 12:46 pm Post subject: |
|
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
Also, I cannot deploy the broker even after I remove the extra code.
FYI.
Thanks |
|
| Back to top |
|
|
| skn |
| Posted: Thu Dec 18, 2003 12:54 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
Assume your output queue had put disabled or full,the broker cannot put the message and tries to roll it back to the input queue(depending on the transaction property).based on the backout count ,it tries to process it again.Since it cant put to the queue the message gets rolled back again.
Why dont you try connecting the catch terminal. |
|
| Back to top |
|
|
| skn |
| Posted: Thu Dec 18, 2003 12:58 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
have you tried a forced deploy?
If even that doesnt work, stop the broker , remove the message from the queue and issue a deploy after starting it again. |
|
| Back to top |
|
|
| MQGuy2000 |
| Posted: Thu Dec 18, 2003 1:48 pm Post subject: |
|
|
Centurion
Joined: 20 Jul 2003
Posts: 131
|
I had to stop the broker and redeploy again.
I printed the exception. from log. Can you pl. see and let me know if you get any clues why it is happeneing.
[color=blue]----(0x1000000)RecoverableException = (
(0x3000000)File = 'F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp'
(0x3000000)Line = 536
(0x3000000)Function = 'ImbDataFlowNode::createExceptionList'
(0x3000000)Type = 'ComIbmComputeNode'
(0x3000000)Name = 'cc814a8a-f900-0000-0080-e7089ea5aebc'
(0x3000000)Label = 'MSGFLOW2.Compute1'
(0x3000000)Text = 'Node throwing exception'
(0x3000000)Catalog = 'WMQIv210'
(0x3000000)Severity = 3
(0x3000000)Number = 2230
(0x1000000)ParserException = (
(0x3000000)File = 'F:\build\S000_P\src\MTI\MTIforBroker\GenXmlParser2\XmlImbParser.cpp'
(0x3000000)Line = 355
(0x3000000)Function = 'ImbXmlParser::parseRightSibling'
(0x3000000)Type = ''
(0x3000000)Name = ''
(0x3000000)Label = ''
(0x3000000)Text = 'XML Parsing Errors have occurred'
(0x3000000)Catalog = 'WMQIv210'
(0x3000000)Severity = 3
(0x3000000)Number = 5009
(0x1000000)ParserException = (
(0x3000000)File = 'F:\build\S000_P\src\MTI\MTIforBroker\GenXmlParser2\XmlBrokerAsgardParser.cpp'
(0x3000000)Line = 677
(0x3000000)Function = 'XmlBrokerAsgardParser::error'
(0x3000000)Type = ''
(0x3000000)Name = ''
(0x3000000)Label = ''
(0x3000000)Text = 'An error has been reported by the BIPXML4C component.'
(0x3000000)Catalog = 'WMQIv210'
(0x3000000)Severity = 3
(0x3000000)Number = 5004
(0x1000000)Insert = (
(0x3000000)Type = 2
(0x3000000)Text = '81'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = ''
)
(0x1000000)Insert = (
(0x3000000)Type = 2
(0x3000000)Text = '1'
)
(0x1000000)Insert = (
(0x3000000)Type = 2
(0x3000000)Text = '4'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'There are more end tags than start tags'
)
(0x1000000)Insert = (
(0x3000000)Type = 5
(0x3000000)Text = 'XML'
)
)
)
)
)
--[/color]
esql code
-------------SET OutputRoot = InputRoot;
SET OutputRoot.XML.OuterMessage.field1 = 'TRY AGAIN';
My Message
-------------
<?xml version="1.0" encoding="UTF-8"?>
<OuterMessage>
<field1> 1</field1>
<field2> 1</field2>
<field3> 1</field3>
<field4> 1</field4>
<field5> 1</field5>
</OuterMessage> |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Dec 18, 2003 2:14 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| -------------SET OutputRoot = InputRoot; |
Do you really want to do that.
I'd suggest using the 'Copy Message Headers'.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| skn |
| Posted: Thu Dec 18, 2003 2:24 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
| The exception suggests something wrong with your message. Are you sure your are putting in the same message as you listed(which seems to be fine).Why dont you try using a different message. |
|
| Back to top |
|
|
|
|
