BizTalk 2004 :: Orchestration timeout not working

Tech-Archive recommends: Fix windows errors by optimizing your registry


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?

The result is my error message is never getting back to the user because the SOAP timeout of 120 seconds has long since been triggered.

I could use some help.

BA
http://biztalkia.blogspot.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)
  • Re: BizTalk 2004 :: Orchestration timeout not working
    ... I've encountered a very strange problem with my orchestration's timeout ... I have a request-response operation via SOAP. ... My orchestration has a base Long Running Transaction of 70 seconds ... Inside the orchestration I have scope shape A (Long Running Transaction of ...
    (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)