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 » Error handling question

Post new topic  Reply to topic
 Error handling question « View previous topic :: View next topic » 
Author Message
kwelch
PostPosted: Tue Aug 13, 2002 10:06 am    Post subject: Error handling question Reply with quote

Master

Joined: 16 May 2001
Posts: 255

Hi,

I have a scenario I would like to run by this forum to see how they would handle this situation.

We have a messageflow where on the input node we define the Domain as MRM, format as CWF, MessageSet and type are set correctly. This goes to a compute node which attempts to process the message and convert it to xml and then goes to the output node. Simple enough. So now we are trying to incorporate error handling. If for some reason the message is bad, we want to, change the expiry to unlimited and persistence of the original message and have it go to the Fail Queue. Then we want to send a reply back to the sender saying 'your message made it to the WMQI flow but it could not be processed'. Today they just get a 2033 time out and don't know where the problem occurs.

We thought we had this set up and created a subflow to do this, but when we put a bad message it just sits on the Input Queue and nothing happens.

How would some of you approach this? Thanks for any tips!

Karen
Back to top
View user's profile Send private message Send e-mail
kirani
PostPosted: Tue Aug 13, 2002 10:15 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

need more information ..
1. Do you have any backout queue defined for the input queue?
2. What is your Backout Threshold set to?
3. Do you have MQInput's catch and failure terminal connected?
4. Where is your sub-flow connected/listening to?
5. Do you have DLQ defined for the queue manager?
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
kwelch
PostPosted: Tue Aug 13, 2002 10:56 am    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 255

Hi Kiran,

In answer to your questions:

1. no backout queue
2. Backout threshold = 0
3/4. The input's Fail was wired to the error subflow - sorry forgot to mention that!!! the Catch was wired to a throw node
5. Yes we do have a DLQ

When I unwire the Fail and Catch the message does go to the DLQ.

Karen
Back to top
View user's profile Send private message Send e-mail
kirani
PostPosted: Tue Aug 13, 2002 11:31 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Karen,

If there is a parsing error at MQInput node itself, your message will be propagated to the failure terminal of the MQInput node. Could you explain your error sub-flow here? If there is an error in error sub-flow itself, your message will roll-back to the MQInput node and it will keep on looping in the failure path.

You could add a try-catch node in the beginning of your error sub-flow and add a Trace node to the Catch terminal of TryCatch node. In the Trace node, print ExceptionList. This way you will know why is your error-subflow failing and message is looping.

Make sure you don't print ${Root} in any of the trace node in your failure sub-flow. This will force the parser to parse input message and it will fail (throw Exception) for bad input message.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
kwelch
PostPosted: Tue Aug 13, 2002 11:49 am    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 255

Hi Kiran,

The error subflow is set up in the following manner:

InputTerminal ---> Compute Node(change expiry and persistence) ---> MQOutputNode(FailQ)
| ---> Compute Node(Set Pass CorrelID) ---> Compute Node(Format reply message) ---> MQOutputNode(ReplytoQ)

There is definitely an error on the input node because when I wire the fail node to just a queue it ends up there, otherwise the DLQ. So it would seem that the subflow does have a problem and we are in that looping state you mentioned. The subflow has promoted items and I wonder if we are not putting them in correctly. You have given me some good sugestions of things to try and I will do that. Thanks!

Karen
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 » Error handling question
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.