ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » (Really) strange behaviour with validate options and rcd

Post new topic  Reply to topic
 (Really) strange behaviour with validate options and rcd « View previous topic :: View next topic » 
Author Message
jfluitsm
PostPosted: Thu Feb 23, 2006 2:26 am    Post subject: (Really) strange behaviour with validate options and rcd Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

I run into a strange problem with the validate options.

Environment: WBIMB 5.0 FP06 on Windows.

Flow synopsis:
MQInput with validate content and value, complete, exception and MRM XML-schema.
- out terminal processing: transform message and put to out-queue, put will fail because of typo in MQOuput-node
- catch terminal processing: Handling Properties, MQMD and ExceptionList but not the message contents and rethrow at end of processing.
- failure terminal: rcd to blob in order to save the original message.

Case 1: not well-formed or well-formed but not valid message.
Message goes direct to failure terminal with an ExceptionList as expected. The rcd to blob works and message is processed as designed.

Case 2: well-formed and valid.
1. Message goes to out-terminal and will fail at the MQOutput node.
2. Message goes to catch-terminal, error is handled and exception is rethrown (throw node).
3. Message goes to failure terminal with an ExceptionList indicating that it fails due to a previous backout.
So far so good, this is what I was expecting.
4. rcd to blob fails, now I have an exceptionlist stating that the message validation fails.

I build another flow as test:
Input node as above, catch and failure wired to trace, out wired to rcd to blob.
1. not well-formed or not-valid goes to failure terminal.
2. well-formed and valid goes to out terminal, rcd to blob fails with validation error.

Someone knwos what is going on?
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
kimbert
PostPosted: Thu Feb 23, 2006 3:39 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
rcd to blob fails with validation error
Can you quote the exact error message ( the term 'validation error' has a very specific meaning, and I want to be sure that I understand what you mean).
Back to top
View user's profile Send private message
javaforvivek
PostPosted: Thu Feb 23, 2006 9:15 pm    Post subject: Reply with quote

Master

Joined: 14 Jun 2002
Posts: 282
Location: Pune,India

Can you also show us your complete message flow along with the error handling subflow?
I have a feeling that when you rethrow the message from Throw Node,
it is not the original message that is thrown back to the input node, but the message containg exception list.

Let us know the input (valid and well-formed) message, in which case you are getting this error, as well the messages at different stages of the processing.
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
jfluitsm
PostPosted: Fri Feb 24, 2006 3:54 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

The error message I got is the BIP5371E. Message Validation Failure.

The problem is not the throw.

I made a test flow:
MQInput (out) --> (in) RCD (out) --> (in) Trace.
The catch and failure are wired to a Trace node.
Settinge for MQInput and RCD are the same as the original flow.

- Not well-formed or not-valid messages go straight to the failure terminal as expected.
- valid message goes from out terminal to the RCD, the rcd fails with the BIP5371E message.

I have raised a pmr.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
kimbert
PostPosted: Fri Feb 24, 2006 6:17 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Hmm. That's a genuine MRM validation error. What are the parameters on the RCD node? Have you accidentally set the Domain to 'MRM'.
Back to top
View user's profile Send private message
jfluitsm
PostPosted: Mon Feb 27, 2006 1:12 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

Nope, I use BLOB. But thinking of it, I don't reset all other fields, will try this tomorrow.

BTW. I ran the same flow in WMB V6 without any problem.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » (Really) strange behaviour with validate options and rcd
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.