| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message going in error queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| wbimb |
 Posted: Wed Apr 27, 2011 9:35 pm Post subject: Message going in error queue |
 |
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
I have a broker which has 12 execution group when I am doing testing this is the issue i am facing
For a particular interface:
1. I stop all the message flow except the one i am testing and then i put a message and it lands into right output queue
2. All the message flows are started and then i put a message and then it goes into error queue with the below error in queue
Error><FlowName>TxTriggerScriptsMsgFlow</FlowName><TimeStamp>2011-04-27 13:29:1
5.436549</TimeStamp><ErrorDetail><RecoverableException><File>/build/S610_P/src/D
ataFlowEngine/ImbComputeNode.cpp</File><Line>464</Line><Function>ImbComputeNode:
:evaluate</Function><Type>ComIbmComputeNode</Type><Name>TxTriggerScriptsMsgFlow#
FCMComposite_1_1</Name><Label>TxTriggerScriptsMsgFlow.Compute</Label><Catalog>BI
Pv610</Catalog><Severity>3</Severity><Number>2230</Number><Text>Caught exception
and rethrowing</Text><RecoverableException><File>/build/S610_P/src/DataFlowEngi
ne/ImbRdl/ImbRdlStatementGroup.cpp</File><Line>602</Line><Function>SqlStatementG
roup::execute</Function><Type>ComIbmComputeNode</Type><Name>TxTriggerScriptsMsgF
low#FCMComposite_1_1</Name><Label>TxTriggerScriptsMsgFlow.Compute</Label><Catalo
g>BIPv610</Catalog><Severity>3</Severity><Number>2488</Number><Text>Error detect
ed, rethrowing</Text><Insert><Type>5</Type><Text>.TxTriggerScriptsMsgFlow_Comput
e.Main</Text></Insert><Insert><Type>5</Type><Text>8.3</Text></Insert><Insert><Ty
pe>5</Type><Text>SET Environment.variables.INTERFACE_NAME = InputBody.Outbound.F
lowName;</Text></Insert><RecoverableException><File>/build/S610_P/src/DataFlowEn
gine/ImbRdl/ImbRdlFieldRef.cpp</File><Line>2390</Line><Function>SqlFieldReferenc
e::evaluate</Function><Type>ComIbmComputeNode</Type><Name>TxTriggerScriptsMsgFlo
w#FCMComposite_1_1</Name><Label>TxTriggerScriptsMsgFlow.Compute</Label><Catalog>
BIPv610</Catalog><Severity>3</Severity><Number>2498</Number><Text>Navigation err
or</Text><Insert><Type>5</Type><Text>.TxTriggerScriptsMsgFlow_Compute.Main</Text
></Insert><Insert><Type>5</Type><Text>8.46</Text></Insert><Insert><Type>2</Type>
<Text>2</Text></Insert><ParserException><File>/build/S610_P/src/MTI/MTIforBroker
/GenXmlParser2/XmlImbParser.cpp</File><Line>633</Line><Function>XmlImbParser::pa
rseFirstChild</Function><Type></Type><Name></Name><Label></Label><Catalog>BIPv61
0</Catalog><Severity>3</Severity><Number>5009</Number><Text>XML Parsing Errors h
ave occurred</Text><ParserException><File>/build/S610_P/src/MTI/MTIforBroker/Gen
XmlParser2/XmlBrokerAsgardParser.cpp</File><Line>723</Line><Function>XmlBrokerAs
gardParser::error</Function><Type></Type><Name></Name><Label></Label><Catalog>BI
Pv610</Catalog><Severity>3</Severity><Number>5004</Number><Text>An error has bee
n reported by the BIPXML4C component.</Text><Insert><Type>2</Type><Text>186</Tex
t></Insert><Insert><Type>5</Type><Text></Text></Insert><Insert><Type>2</Type><Te
xt>1</Text></Insert><Insert><Type>2</Type><Text>1</Text></Insert><Insert><Type>5
</Type><Text>Invalid document structure </Text></Insert><Insert><Type>5</Type><T
ext>XML</Text></Insert></ParserException></ParserException></RecoverableExceptio
n></RecoverableException></RecoverableException></ErrorDetail></Error>
When I send this to MQadmin they tell me that the issue is with the code, but I wonder how can it have issue with the code when it works fine when all the message flows are stopped. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Apr 27, 2011 11:43 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
How about multiple Flows reading from the same Queue?
did you check the IPPROCS/Open Input Count on the UnputQueue in both cases?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| flahunter |
| Posted: Thu Apr 28, 2011 12:01 am Post subject: |
|
|
Acolyte
Joined: 30 Oct 2008
Posts: 62
|
| Quote: |
| XML Parsing Errors have occurred |
Maybe mutiple flows read the same input queue, maybe another flow read the output queue. |
|
| Back to top |
|
|
| wbimb |
| Posted: Thu Apr 28, 2011 12:48 am Post subject: |
|
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
Multiple message flows are not reading the same input queue.
But yes all of the message flows are putting message on the same output queue.
But how can this affect the message to go to error queue |
|
| Back to top |
|
|
| khudania |
| Posted: Thu Apr 28, 2011 3:17 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
In order to identify the actual issue, I guess you need to try to start each message flow one by one and see which message flow start actually causes the issue.
Elimination Theory
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| Gerd-in-ZA |
| Posted: Thu Apr 28, 2011 9:30 am Post subject: |
|
|
Novice
Joined: 13 Sep 2006
Posts: 14
Location: Johannesburg, South Africa
|
It wouldn't be whatever flow reads the output queue that detects that the message your flow has created is not well-formed XML? If you can get MB to render an invalid XML message it wouldn't be discovered until something else reads it and fails parsing it.
You didn't share with us details like "does the flow name in the exception list mean anything to you?" "What is the content of the message buffer at the time of error?" "Could one of the other flows put a message to your flow's input queue?" (In addition to your good test message, of course.) "Is the flow processing from the output queue also started after the 'successful' single test?"
Remember, in MQ things tend to happen rather quickly. Your test environment has barely put a message into a queue, and before you can go and look at it something else has taken it away again. Which is why, generally, it is a good idea to start components one after the other, only allowing a message to be consumed once you have seen it at rest in a queue. Some people even, in the unit test phase, put messages onto a second queue, just to look at it.
I don't think your flow does something different when it runs in competition with other flows - that sort of stuff is not all that easy to do in MB. But some of the other scenarios are much more likely.
So, try to think through some scenarios, eliminate some of the unrelated flows in those 12 execution groups, run and read a user trace; then, if nothing pops up, come back here with lots more details.
_________________
-- Gerd -- |
|
| 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
|
|
|
|
