| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Missing Element in OutputRoot |
« View previous topic :: View next topic » |
| Author |
Message
|
| kimbert |
 Posted: Fri Dec 01, 2006 5:15 am Post subject: |
 |
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Let's take a step back and look at this problem:
This error
| Code: |
''InputBody.http://schemas.xmlsoap.org/soap/envelope/:Body.urn:ec.europa.eu:taxud:vies:services:checkVat:types:checkVatResponse.vatNumber''. The result was ''EMPTY ROW''.
BIP2567I: Node 'Check_VAT.Compute': Assigning NULL to ''OutputRoot.MRM.Valid'', thus deleting it. |
allows two possibilities.
1. The message tree is incorrect
2. The ESQL path is incorrect.
If we assume 2., there are several possible faults in a path
- wrong namespace(s)
- wrong name(s)
- wrong correlation names ( not relevant here, I think ).
In order to diagnose this problem, we need a trace of ${Root} ( all of it, please ). It should be simple to spot the problem from there.
And I agree that 'TDS1' looks very strange. Are you sure you posted the correct code snippet? |
|
| Back to top |
|
 |
| bullaydin |
| Posted: Fri Dec 01, 2006 6:00 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2006
Posts: 25
Location: Germany
|
I've sent complete trace (inc. ${Root}), after HTTPRequest node.
| Code: |
2006-12-01 14:53:47.875835~13942704 UserTrace BIP6061I: Parser type ''HTTPResponseHeader'' created on behalf of node 'Check_VAT.Q.WEBSERVICE_IN' to handle portion of incoming message of length '227' bytes beginning at offset '0'. Parser type selected based on value ''WSRSPHDR'' from previous parser.
2006-12-01 14:53:47.876098~13942704 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Check_VAT.Q.WEBSERVICE_IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2006-12-01 14:53:47.876331~13942704 UserTrace BIP6061I: Parser type ''HTTPResponseHeader'' created on behalf of node 'Check_VAT.Q.WEBSERVICE_IN' to handle portion of incoming message of length '227' bytes beginning at offset '0'. Parser type selected based on value ''WSRSPHDR'' from previous parser.
2006-12-01 14:53:47.876602~13942704 UserTrace BIP6061I: Parser type ''MRM'' created on behalf of node 'Check_VAT.Q.WEBSERVICE_IN' to handle portion of incoming message of length '615' bytes beginning at offset '227'. Parser type selected based on value ''MRM'' from previous parser.
2006-12-01 14:53:47.877681~13942704 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'Check_VAT.HTTP Request'.
2006-12-01 14:53:47.877803~13942704 UserTrace BIP2539I: Node 'Check_VAT.Trace': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2006-12-01 14:53:47.877975~13942704 UserTrace BIP4060I: Data ''(
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:Body = (
(0x01000000)urn:ec.europa.eu:taxud:vies:services:checkVat:types:checkVatResponse = (
(0x03000000):countryCode = 'AT'
(0x03000000):vatNumber = 'wer'
(0x03000000):requestDate = DATE '2006-12-01'
(0x03000000):valid = FALSE
(0x03000000):name = ''
(0x03000000):address = ''
)
)
)
'' from trace node 'Check_VAT.Trace'.
The trace node 'Check_VAT.Trace' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2006-12-01 14:53:47.878047~13942704 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Check_VAT.Trace'.
The trace node 'Check_VAT.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2006-12-01 14:53:47.878185~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''DECLARE ns NAMESPACE 'urn:ec.europa.eu:taxud:vies:services:checkVat:types';'' at ('.ns', '1.1').
2006-12-01 14:53:47.878227~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''DECLARE tns NAMESPACE 'http://schemas.xmlsoap.org/soap/envelope/';'' at ('.tns', '1.1').
2006-12-01 14:53:47.878276~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''BEGIN ... END;'' at ('.Check_VAT_Compute.Main', '2.2').
2006-12-01 14:53:47.878318~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.HTTPResponseHeader = NULL;'' at ('.Check_VAT_Compute.Main', '9.2').
2006-12-01 14:53:47.878383~13942704 UserTrace BIP2567I: Node 'Check_VAT.Compute': Assigning NULL to ''OutputRoot.HTTPResponseHeader'', thus deleting it.
2006-12-01 14:53:47.878429~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.Properties.MessageType = 'VAT_Response';'' at ('.Check_VAT_Compute.Main', '12.3').
2006-12-01 14:53:47.878524~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value '''VAT_Response''' to field / variable ''OutputRoot.Properties.MessageType''.
2006-12-01 14:53:47.878566~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.Properties.MessageFormat = 'TDS1';'' at ('.Check_VAT_Compute.Main', '13.2').
2006-12-01 14:53:47.878604~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value '''TDS1''' to field / variable ''OutputRoot.Properties.MessageFormat''.
2006-12-01 14:53:47.878639~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.Properties.MessageSet = 'VAT_Response';'' at ('.Check_VAT_Compute.Main', '14.2').
2006-12-01 14:53:47.878677~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value '''VAT_Response''' to field / variable ''OutputRoot.Properties.MessageSet''.
2006-12-01 14:53:47.878715~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''CREATE NEXTSIBLING OF OutputRoot.Properties DOMAIN 'MQMD';'' at ('.Check_VAT_Compute.Main', '18.3').
2006-12-01 14:53:47.878784~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.MQMD = Environment.MQMD;'' at ('.Check_VAT_Compute.Main', '19.3').
2006-12-01 14:53:47.878833~13942704 UserTrace BIP2539I: Node 'Check_VAT.Compute': Evaluating expression ''Environment.MQMD'' at ('.Check_VAT_Compute.Main', '19.25'). This resolved to ''Environment.MQMD''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='MQMD' Value=NULL''.
2006-12-01 14:53:47.878864~13942704 UserTrace BIP2568I: Node 'Check_VAT.Compute': Copying sub-tree from ''Environment.MQMD'' to ''OutputRoot.MQMD''.
2006-12-01 14:53:47.878974~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.MRM.SQLIDN = 2;'' at ('.Check_VAT_Compute.Main', '24.3').
2006-12-01 14:53:47.879096~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value ''2'' to field / variable ''OutputRoot.MRM.SQLIDN''.
2006-12-01 14:53:47.879142~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.MRM.APAIDN = 0;'' at ('.Check_VAT_Compute.Main', '25.3').
2006-12-01 14:53:47.879180~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value ''0'' to field / variable ''OutputRoot.MRM.APAIDN''.
2006-12-01 14:53:47.879219~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.MRM.Request_date = '10.10.2006';'' at ('.Check_VAT_Compute.Main', '26.3').
2006-12-01 14:53:47.879268~13942704 UserTrace BIP2566I: Node 'Check_VAT.Compute': Assigning value '''10.10.2006''' to field / variable ''OutputRoot.MRM.Request_date''.
2006-12-01 14:53:47.879310~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''SET OutputRoot.MRM.Valid = InputBody.tns:Body.ns:checkVatResponse.vatNumber;'' at ('.Check_VAT_Compute.Main', '27.9').
2006-12-01 14:53:47.879341~13942704 UserTrace BIP2543I: Node 'Check_VAT.Compute': ('.Check_VAT_Compute.Main', '27.36') : Failed to navigate to path element number '2' because it does not exist.
2006-12-01 14:53:47.879386~13942704 UserTrace BIP2539I: Node 'Check_VAT.Compute': Evaluating expression ''InputBody.tns:Body.ns:checkVatResponse.vatNumber'' at ('.Check_VAT_Compute.Main', '27.36'). This resolved to ''InputBody.http://schemas.xmlsoap.org/soap/envelope/:Body.urn:ec.europa.eu:taxud:vies:services:checkVat:types:checkVatResponse.vatNumber''. The result was ''EMPTY ROW''.
2006-12-01 14:53:47.879463~13942704 UserTrace BIP2567I: Node 'Check_VAT.Compute': Assigning NULL to ''OutputRoot.MRM.Valid'', thus deleting it.
2006-12-01 14:53:47.879505~13942704 UserTrace BIP2537I: Node 'Check_VAT.Compute': Executing statement ''RETURN TRUE;'' at ('.Check_VAT_Compute.Main', '29.3').
2006-12-01 14:53:47.879573~13942704 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'Check_VAT.Compute'.
2006-12-01 14:53:47.880302~13942704 UserTrace BIP2638I: The MQ output node 'Check_VAT.Q.WEBSERVICE_OUT' attempted to write a message to queue ''Q.WEBSERVICE_OUT'' connected to queue manager ''QM_BROKER_TEST''. The MQCC was '0' and the MQRC was '0'.
2006-12-01 14:53:47.880352~13942704 UserTrace BIP2622I: Message successfully output by output node 'Check_VAT.Q.WEBSERVICE_OUT' to queue ''Q.WEBSERVICE_OUT'' on queue manager ''QM_BROKER_TEST''.
2006-12-01 14:53:47.880504~13942704 UserTrace BIP2638I: The MQ output node 'Check_VAT.RMTQ.TEST' attempted to write a message to queue ''RMTQ.TEST'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2006-12-01 14:53:47.880527~13942704 UserTrace BIP2622I: Message successfully output by output node 'Check_VAT.RMTQ.TEST' to queue ''RMTQ.TEST'' on queue manager ''''.
2006-12-01 14:53:47.881366~13942704 Error BIP2648E: Message backed out to a queue; node 'Check_VAT.Q.WEBSERVICE_IN'.
Node 'Check_VAT.Q.WEBSERVICE_IN' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2006-12-01 14:53:47.882190~13942704 UserTrace BIP2638I: The MQ output node 'Check_VAT.Q.WEBSERVICE_IN' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''QM_BROKER_TEST''. The MQCC was '0' and the MQRC was '0'.
2006-12-01 14:53:47.882339~13942704 UserTrace BIP2615I: The WebSphere MQ input node 'Check_VAT.Q.WEBSERVICE_IN' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required. |
I am sure that it was the correct code snippet....
_________________
*************************
" Sharing knowledge better than having it ."
http://www.openpoint.de |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Dec 01, 2006 8:21 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Did you code your namespace declares or did the code assist do it for you? I'm assuming your using MRM on the HTTPRequest node.
If you coded them, comment them out and use the code assist while recoding your logic. You are using V6, right?
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| bullaydin |
| Posted: Mon Dec 04, 2006 12:44 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2006
Posts: 25
Location: Germany
|
hi ,
yes i am using v6 , and also used code assist ..
_________________
*************************
" Sharing knowledge better than having it ."
http://www.openpoint.de |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Dec 04, 2006 4:12 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
gregop said:
| Quote: |
If thats the full root tree then there is no message domain indicated in the trace. InputBody = InputRoot.DOMAIN therefore I'd expect InputBody would return null if no message domain assigned for the response message.
Try specifying XML in your HTTPRequest message DOMAIN or perhaps you can reference the HTTP response directly using InputRoot instead of InputBody. |
I agree. I would expect the root of the message tree to be a domain name like 'XMLNS' or 'XMLNSC'. So where is the name 'Data' coming from? What domain have you specified in the http request node? |
|
| Back to top |
|
|
| bullaydin |
| Posted: Mon Dec 04, 2006 4:44 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2006
Posts: 25
Location: Germany
|
| Quote: |
| So where is the name 'Data' coming from? What domain have you specified in the http request node? |
I've specified MRM Domain in httpRequest node.
_________________
*************************
" Sharing knowledge better than having it ."
http://www.openpoint.de |
|
| Back to top |
|
|
| bullaydin |
| Posted: Mon Dec 04, 2006 4:52 am Post subject: |
|
|
Apprentice
Joined: 16 Feb 2006
Posts: 25
Location: Germany
|
thanks for your help guys,
I've changed domain type into XMLNSC and now everything is OK.
thnks again
_________________
*************************
" Sharing knowledge better than having it ."
http://www.openpoint.de |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
