Behavior of a Transaction

[Former Member]

I am just thinking, can each transaction's behaviour configurable in the sense of existence. For example a transaction reading a file and parse it. This transaction's thread should only exist once when it is running.

Let say the transaction takes 1-3 minutes each time it runs, and it is scheduled at every 2 minutes. So collision will occur if the previous thread is running. Can we configure this transaction so that if the 2nd thread started to run, it will fail untill the nex scheduled time?

I know I could implement this in the beginning of the transaction with a flag's check, but I am just wondering if MII does have the capability to do that of its own.

[Former Member]

Hi..

As far as my knowledge goes, if a scheduler is ready for second run and first run transaction is still running then MII won't allow transaction for second run.

I just tested this. It works as per my understanding.

Hope this solves your query.

Best Regards,

Kedar

Edited by: Kedar Shewalkar on Jun 23, 2011 5:52 PM

[Former Member]

I have found out someting interestingly

[Former Member]

Yes, an interesting thread indeed.

Thanks..

Best Regards,

Kedar