Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

BizTalk Timeout error

49 views
Skip to first unread message

Sourav Dutta Gupta

unread,
Aug 29, 2006, 2:42:01 PM8/29/06
to

Hi,

I am having some problem with Biztalk. I have developed an Orchestration and
published the same as web service. Internally this Orchestration consumed
another web service. Often this Orchestration gets timed out. Error is logged
in the Event Viewer as follows:

1. A request-response for the "SOAP" adapter at receive location
"/Hillary_ExtraAvailability_Proxy/ExtraAvailabilityOrchestration_orch_ExtraAvailability_web_Port_ExtraAvailability.asmx"
has timed out before a response could be delivered.

2. The adapter failed on an attempt to transmit a message going to send port
with the address
"/Hillary_ExtraAvailability_Proxy/ExtraAvailabilityOrchestration_orch_ExtraAvailability_web_Port_ExtraAvailability.asmx".
Details: "Application Either Has Timed Out Or Is Timing Out".

Now I want to catch this exception in the Orchestration level itself. I have
tried to use "Microsoft.XLANGs.BaseTypes.TimeoutException" exception block. I
am not sure whether it works or not. I suppose it does not.

Can anyone give me a proper solution to catch this error.

regards
sourav.

Scott Colestock

unread,
Aug 30, 2006, 2:19:47 PM8/30/06
to

If you put a scope around the send/rcv associated with your web service
call, you should be able to just catch System.Exception (you can use
multiple catch blocks if you need finer grained handling.)

Scott Colestock
www.traceofthought.net

Jan Eliasen

unread,
Aug 30, 2006, 3:47:22 PM8/30/06
to
On Tue, 29 Aug 2006 11:42:01 -0700, Sourav Dutta Gupta
<SouravDu...@discussions.microsoft.com> wrote:

>I am having some problem with Biztalk. I have developed an Orchestration and
>published the same as web service. Internally this Orchestration consumed
>another web service. Often this Orchestration gets timed out. Error is logged
>in the Event Viewer as follows:

Sounds more to me that it isn't the calling a web service inside your
orchestration that times out, but the process that handles the call to
YOUR web service has times out. So when your orchestration wants to
send the response back to the caller, this can't be done, because he
has timed out.

So basically, there is no exception inside your orchestration to
catch.

--
eliasen, representing himself and not the company he works for.

private email: j...@eliasen.dk

0 new messages