Indirect transaction timeout

[Marc Morin <ma...@emforium.com>]

We have a condition where ordering a specific product (electronic product) that can take a long time to perform during the finalize stage.  This has to do with the fact that it is a digital subscription, and there is a service attached to the product, and this service creates a new tenant (create database in our case).

This process can take about 50 seconds.   Now, on the service definition for this service call, we define a transaction timeout of 120 seconds, yet this doesn't take affect.

It appears that the tranaction timeout field in the service definition only applies to the first service call that initiates the beginning of the transaction.  This is very unstable and difficult to manage.

Any idea on how difficult it would be to change the behaviour such that the current transaction timeout is set to the maximum of the current invoked service timeout in the model, vs the timeout in the current active transaction?

Noticed that there wasn't a method call on the transaction interface, so would likely need to be non-standard.

Marc Morin
Emforium Group Inc. 
ALL-IN Software™ 
519-772-6824 ext 201 
mmorin@emforium.com