| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XMLNSC Validation |
« View previous topic :: View next topic » |
| Author |
Message
|
| maisief |
 Posted: Tue Dec 23, 2008 7:10 am Post subject: XMLNSC Validation |
 |
|
Newbie
Joined: 23 Dec 2008
Posts: 4
|
I am trying to validate an incoming message in a flow using a validate node and the XMLNSC domain. The only message related to the validation that can I see in the trace is the following:
| Code: |
<RecoverableException timestamp="2008-12-23 14:45:29.088199" thread="9384" function="ImbValidateNode::evaluate" type="ComIbmValidateNode" name="PublishMsg#FCMComposite_1_4" label="PublishMsg.Validate Event Message" text="'Domain, set or type check failed'" catalog="BIPv610" number="4162" file="F:\build\S610_P\src\DataFlowEngine\BasicNodes\ImbCheckNode.cpp" line="387">
<Insert type="string">'XMLNSC'</Insert>
<Insert type="string">''</Insert>
<Insert type="string">''</Insert>
<Insert type="string">'XMLNSC'</Insert>
<Insert type="string">'PublishMessages'</Insert>
<Insert type="string">''</Insert>
<Insert type="string">PublishMsg.Validate Event Message</Insert>
|
Is there anyway to get more detail on what the cause of the failure is ? |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Tue Dec 23, 2008 6:44 pm Post subject: Re: XMLNSC Validation |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
You could run a usertrace to get the complete text of the error message. Depending on which platform the broker is running on, you could also try looking in the event viewer or system log; sometimes exceptions show up there too.
Failing that, you could look up the error (number="4162") in the toolkit help Diagnostic Messages, plugging in any provided Inserts yourself:
| Code: |
BIP4162
Message
A non-matching message is rejected by Check node 'PublishMsg.Validate Event Message'.
Values received: domain 'XMLNSC'; set ''; type ''.
Values expected: domain 'XMLNSC'; set 'PublishMessages'; type ''.
Explanation
The Check node 'PublishMsg.Validate Event Message' has detected that the input message did not match the specified criteria, and that a message flow processing node is not attached to its failure terminal.
An exception is generated.
Response
Identify why invalid messages are either being sent into the broker or being generated, and correct the problem if necessary.
If you have specified the Check node properties incorrectly, correct them, and redeploy the message flow. |
On a side note, the text of the error message refers to a "Check node", rather than a "Validate node". This looks like an oversight in updating the documentation. The "Validate node" is supposed to replace the (now deprecated) "Check node". |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 23, 2008 10:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If you want to validate an XML document, why not import the schema into a message set?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| maisief |
| Posted: Wed Dec 24, 2008 1:22 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2008
Posts: 4
|
| Vitor wrote: |
| If you want to validate an XML document, why not import the schema into a message set? |
I am using the schema in a message set. If I validate an XML file against schema I normally expect to be told what is wrong not just that something is wrong. The annoying thig is that the XML file is valid according to other XML tools; Eclipse & XML Notepad. |
|
| Back to top |
|
|
| maisief |
| Posted: Wed Dec 24, 2008 2:35 am Post subject: Re: XMLNSC Validation |
|
|
Newbie
Joined: 23 Dec 2008
Posts: 4
|
| rekarm01 wrote: |
You could run a usertrace to get the complete text of the error message. Depending on which platform the broker is running on, you could also try looking in the event viewer or system log; sometimes exceptions show up there too.
Failing that, you could look up the error (number="4162") in the toolkit help Diagnostic Messages, plugging in any provided Inserts yourself:
| Code: |
BIP4162
Message
A non-matching message is rejected by Check node 'PublishMsg.Validate Event Message'.
Values received: domain 'XMLNSC'; set ''; type ''.
Values expected: domain 'XMLNSC'; set 'PublishMessages'; type ''.
Explanation
The Check node 'PublishMsg.Validate Event Message' has detected that the input message did not match the specified criteria, and that a message flow processing node is not attached to its failure terminal.
An exception is generated.
Response
Identify why invalid messages are either being sent into the broker or being generated, and correct the problem if necessary.
If you have specified the Check node properties incorrectly, correct them, and redeploy the message flow. |
On a side note, the text of the error message refers to a "Check node", rather than a "Validate node". This looks like an oversight in updating the documentation. The "Validate node" is supposed to replace the (now deprecated) "Check node". |
rekarm01,
Thanks for the pointer, when I looked at my trace the message set wasn't set on the incoming message so I changed this on the input node and now it validates.
 |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jan 01, 2009 4:40 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
So can I quote you as saying that User Trace helped you to diagnose your problem?  |
|
| Back to top |
|
|
| maisief |
| Posted: Mon Jan 05, 2009 12:45 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2008
Posts: 4
|
You can  |
|
| 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
|
|
|
|
