Posted: Mon Dec 04, 2006 11:19 am Post subject: Can a Message Flow Disable Itself?
Novice
Joined: 02 May 2005 Posts: 15 Location: Pittsburgh, PA
I'm using a vrs 5.0 broker messge flow to insert records from MQ messages into a remote Oracle database. This can be implemented as either a DataInsert Node or as an ESQL module of a Compute node. An external stored procedure call is aother option we're looking at that might offer some performance advantages.
Given certain errors associated with the remote database, e.g., database not available, is there a way to use the THROW function following a DataInsert failure, or certain SQLCODE value after an ESQL Insert to STOP the message flow so that messages waiting on an input queue are not processed? (Of course, we do not want to interrupt other messages flows running on the broker)
What I've read so far indicates that the messages should be routed to a message failures queue. I want to know if there are any other options that would stop the message flow from attempting to connect to a corrupt database.
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