Re: BizTalk 2004 :: Orchestration timeout not working

BA,

Hello,

I've encountered a very strange problem with my orchestration's timeout
properties.

I have a request-response operation via SOAP. SOAP has a timeout of 120
seconds.

My orchestration has a base Long Running Transaction of 70 seconds

Inside the orchestration I have scope shape A (Long Running Transaction of
65 seconds) with a catch block to send error responses back to the SOAP
port in case of errors or timeouts.

Inside scope A I have an Atomic scope B (retry = false) with a timeout of
60 seconds.

In scope B I am calling rules, a .net component and then another set of
rules.
The error is occuring because of a bug in the .net component which is
causing
the component to hang. To catch it, scope B should timeout within 65
seconds
and cascade to the catch block of scope A. I am in fact reaching the catch
block, but why is it taking 220 seconds?

I *think* that the timeout on atomic transaction scopes (and possibly on
long running ones, as well) is not meant to be hard. In other words, it does
not mean that it will "break" processing if the timeout is exceeded, but
rather means that if execution takes longer than the timeout time, the
transaction will abort (heck, that's just what it means for DTC
transactions, so it would make sense).

You might have to find a way of doing the hard break at the code level
itself, possibly by wrapping the problematic compoonent inside another one
that enforces it (should be fairly trivial to do so by simply starting the
call to the real component async and then doing a wait on an event or some
other control mechanism with a timeout).

--
Tomas Restrepo
tomasr@xxxxxxxx
http://www.winterdom.com/


.

Relevant Pages

  • Re: BizTalk 2004 :: Orchestration timeout not working
    ... I've done some more research and yes, the transaction doesnt do a hard break on the step being executed. ... I'd always worked with the assumption that a 60 second timeout would last 60 seconds. ... It would be nice to run my .net component inside of a branch and have a delay in another branch, whichever one finishes first dictates the next processing. ... Inside the orchestration I have scope shape A (Long Running ...
    (microsoft.public.biztalk.general)
  • BizTalk 2004 :: Orchestration timeout not working
    ... I've encountered a very strange problem with my orchestration's timeout properties. ... I have a request-response operation via SOAP. ... Inside the orchestration I have scope shape A with a catch block to send error responses back to the SOAP port in case of errors or timeouts. ... In scope B I am calling rules, a .net component and then another set of rules. ...
    (microsoft.public.biztalk.general)
  • Re: Need help analyzing IISSTATE Log - Query timeouts?
    ... Looks like ADO is trying to cancel the query. ... could be the result of several things (page timeout, ... scope, etc.) ...
    (microsoft.public.inetserver.iis)
  • Transaction timeout on CLR stored procedure
    ... I have a CLR stored procedure that times out after approximately the same duration each time give or take a couple of seconds. ... I've not had any issues with timeouts until now, but I've not had a transaction run this long until now either. ... I've tried setting the Remote Query timeout to 0 and another ridiculously large number, ...
    (microsoft.public.sqlserver.connect)
  • Re: Rollback timeout ???
    ... I actually like and would recommend using the tsql Begin Transaction instead ... the ammount of time the connection remains in the pool. ... As to setting the transaction timeout period for the BeginTransaction API... ... >> create a transaction object, ...
    (microsoft.public.dotnet.framework.adonet)