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 » Unknown terminal of Filter node

Post new topic  Reply to topic
 Unknown terminal of Filter node « View previous topic :: View next topic » 
Author Message
Yanghui
PostPosted: Tue Jun 03, 2003 7:21 am    Post subject: Unknown terminal of Filter node Reply with quote

Disciple

Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland

Hi,

I have a question about Filter node. Hope somebody knows the answer.

If the unknown terminal of a filter node is not connectted and a message is propagated through it, I expect the message would be rolled back but actually what happened to me was that the message was discarded. Is this always true? If it is, which means I have to connect the unknown terminal to pick up the message if I don't want to lose any message. Losing message is always bad. So, to me, it's in the scope of error handling.

Normally, I leave all Failure terminals disconnectted and only connect the Catch terminal of MQInput node to a error-handling subflow to centralize error processing. Because of this strange behavior of Filter node, it seems I have to make an exception for it, which is no good to me.

Does anybody know the better way of handling the Unknown terminal of Filter node? Thanks a lot.

Regards
-Yanghui
Back to top
View user's profile Send private message Send e-mail
shalabh1976
PostPosted: Tue Jun 03, 2003 10:57 am    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

It is precisely for this reason that I connect the unknown terminal to either the true or the false terminal connected node as the case may be.
For me it is mostly the false terminal.
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
kirani
PostPosted: Tue Jun 03, 2003 4:39 pm    Post subject: Reply with quote

Jedi Knight

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

Yanghui,

How about attaching a Throw node to the Unknown terminal of the Filter node? By doing this the message will be rollbacked and will be handled by the Error processing sub-flow.
Propagating a message thru either True, False or Unknown termianl is not considered as an error, so by default it will not throw an exception.
_________________
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
Yanghui
PostPosted: Wed Jun 04, 2003 8:11 am    Post subject: Reply with quote

Disciple

Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland

Many thanks for your replys.

Throw node is a very good idea. It works perfectly in my framework.

Thanks again

-Yanghui
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 » Unknown terminal of Filter node
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.