MQSeries.net :: View topic - Automatically start multiple instances of a Flow

x061294 · Posted: Tue Nov 06, 2007 3:17 am Post subject:

Is there a way to force, in version 6 on Linux Intel, multiple instances of a flow to start up upon broker start?

I ask because I want to start my flow with a timer node, with a 1 second interval. This way I can poll a database for any inserts and act upon them as quickly as possible. We went down the approach of having the Database (Oracle) send the message in to the broker, but it's smallest window was 1 second as well. We also took a look if we could have a trigger on the DB fire off the data via WS since that doesn't have the polling issue, but, then we tie up future inserts waiting for the WS to finish.

We're resigned to polling the DB, so to keep the control in 1 place we're going to have the broker do the polling since it will do the rest of the work within the scope of a transaction. However, even 1 second of polling time means that I lose potentially .99 seconds of time after an insert, and, when I only have a 3 second SLA to get the data out of the DB and up to another system, after doing processing on it, wasting .99 seconds is a lot.

My question/thought would be, can we start up two instances of the flow automatically? I know they wouldn't be polling exactly .5 seconds apart, but, it gives me a warmer and fuzzier feeling knowing that I've shrunk the window down a little at least.

Ideally I'd like to start a number of instances when peak processing is going on so that I have instances always looking to pull data off the DB as fast as it arrives, and then lower that number so I'm not just buring cycles when no records are being written during off peak. Don't know if that will require too much ongoing deployment effort though.