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 » Exception handler / Replay questions...

Post new topic  Reply to topic
 Exception handler / Replay questions... « View previous topic :: View next topic » 
Author Message
CHERIANV
PostPosted: Wed May 26, 2004 8:13 am    Post subject: Exception handler / Replay questions... Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York

Hi,
Can you help on the following ?

a.) We have a common exception handler that we wire to all flows (catch / failure terminals) . The first filter when it gets to the catch is to validate if its a parser exception and in order for that we have the following ExceptionList Validation .

IF (FIELDNAME(ExceptionList.RecoverableException.RecoverableException.ParserException) IS NOT NULL)
OR (FIELDNAME(ExceptionList.RecoverableException.ParserException) IS NOT NULL)
THEN RETURN TRUE;
ELSE RETURN FALSE;
END IF;

If TRUE, we have a RCD to convert the message to BLOB , build an exception header in RHF2 and send the msg. to an exception queue.

Question : Do we really need to convert to BLOB in our exception handler if we have a parser exception on input or output ? Are there any impacts if we dont convert to BLOB ?

b.) We have a replay process to strip off the RFH2 header and and route it back to the input queue after the problem is resolved.

In the event, we have a parser exception, the excp. msg. looks like Properties + MQMD + MQRFH2 + BLOB,

If it fails due to a non-parser exception, the excpt. msg. looks like
Properties+ MQMD + MQRFH2 + XML (or MRM).

Question(s) : The replay process somehow doesnt work for the first scenario (Properties + MQMD + MQRFH2 + BLOB) but works fine for the second scenario . For the replay process, we have the input node accepting a BLOB and a RCD to reparse message domain as XML (if the input msg is supposed to be XML) and that doesnt work..

Any input is appreciated.
Back to top
View user's profile Send private message
catwood2
PostPosted: Thu May 27, 2004 8:30 am    Post subject: Reply with quote

Centurion

Joined: 17 May 2002
Posts: 108

Quote:
Question : Do we really need to convert to BLOB in our exception handler if we have a parser exception on input or output ? Are there any impacts if we dont convert to BLOB ?


From what you describe..you discover parse error and write to an exception queue (that is set to blob domain). I don't see why a RCD is required.

Quote:
If it fails due to a non-parser exception, the excpt. msg. looks like
Properties+ MQMD + MQRFH2 + XML (or MRM).

Question(s) : The replay process somehow doesnt work for the first scenario (Properties + MQMD + MQRFH2 + BLOB) but works fine for the second scenario . For the replay process, we have the input node accepting a BLOB and a RCD to reparse message domain as XML (if the input msg is supposed to be XML) and that doesnt work..

I might be reading this wrong....but, you put a message on the queue that has badly formed XML and pass it thru RCD and replay fails. Are you doing anything to the mal formed XML before passing thru RCD? It doesn't sound like it and I would expect that to fail if it's the case (you didn't do anything). The second scenario works b/c the XML can be parsed etc.

Anyways, far more savvy minds on this board than mine....
Back to top
View user's profile Send private message
CHERIANV
PostPosted: Tue Jun 01, 2004 7:51 am    Post subject: Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York

Thanks for the response!

For the first part . we could use a compute node instead to covert to BLOB but we were wondering if in this scenario we really needed to convert to BLOB if we encounter parser errors. Since the parser errors could be at the input (for an incoming XML) or at the output (for an output MRM) , what will the impact be if we leave the message as-is by not converting to BLOB.

For the second replay part, the parser error occured at the output when converting to MRM in the Compute (XML to MRM transformation) . The transfomration failed due to data overflow problem and is caught by the catch path of exception handler . The input XML msg. is what we're trying to convert to BLOB and send to the exception queue.We dont think we 're doing anything with the XML before passing it thru RCD . We confirmed from the trace that the exception message looks (Properties + MQMD + MQRFH2 + BLOB) . When replaying this message (with input node message domain as BLOB), and an RCD to XML , its failing complaining "BIP5004E : An error has been reported by the BIPXML4C component.Invalid document structure,
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Exception handler / Replay questions...
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.