MQSeries.net :: View topic - Long-running transactions

paranoid221 · Posted: Tue Sep 22, 2009 2:47 am Post subject:

Greetings gentlemen,

I was just asked by somebody here "how long does broker maintain its connection to a given database after the initial connect?".
I can see where they are coming from. They have a few SQLs on the DB2 side which takes about 30 mins to complete once they are invoked and wanted to find out if broker can be used to call that SQL and process the response after the SQL execution has been completed.
I have already given them the following answer: "While I'm sure that no enterprise product would ever maintain connections for that long and broker is no exception, it is not ideal to maintain DB connections for that long. The better bet would be to modify the SQL so that it can insert a new row in a table once its execution is complete. You could then setup a trigger on that table to notify your app so it can complete the rest of the tasks in the workflow from that point on and you wouldn't even have to use broker in this case."

I just wanted to check with you guys on the following:
1) How long does broker wait to timeout the DB connection?
2) Comments on the reply I have given above
3) Is there a support for long-running transactions in broker (although from the documentation I haven't found any)?

Thanks for the time.
paranoid
_________________
LIFE is a series of complex calculations, somewhere multiplied by ZERO.