My internal sysnchronous transaction time is 120 sec. So when I call a PL/Sql procedure using the DB adapter synchronously, my process is throwing Timeout error. In order to come out from this I am thinking to have a Pick activity (similar like 108.Timeouts example) after invoking the DB and then in the PICK activity I want to specify some longer time. But I am wondering if I can give big amount like hours or days which is more than the default time? In this case I hope again the time out will happen in the Pick Activity? mmmmm, am I thinking right?
Or the transaction won't expire unless the Alaram is triggered?
while using a invoke activity that default time sys invocation is used, at the time of use of Pick activity this is a seprate timer and not related to the that timer ... go ahead and implement pick... it will work...
It is not sensible to have a synchronous process with timeouts in hours or days, since the engine holds a thread in memory until it completes, you are therefore holding onto resources which prevents them from being used by other requests, and you will suffer from performance problems. This should really be made an asynchronous process.