Hi all.
I have an orchestration published as web service. Inside it there are two
ports hooked on two web services that call an other orchestration published
as web service. This second orchestration runs for a long time (about 4
minutes) for this reason I receive an exception in the first orchestration,
because the result doesn't come back in time. In the event viewer of BizTalk
I receive the subsequent errors:

Source: XLANG/s
Category: BizTalk Server 2004
Time: 10:45:13 AM
Type: Error
User: N/A
Event ID: 10034
Uncaught exception terminated service
ComposedTransientCounter.ComplexScenario(a6019627-64ba-2309-2d47-11f9c08c5ec
6), instance 468a44fb-94f1-48ba-bd7f-e72235a71cd6
An error occurred while processing the message, refer to the details section
for more information
Exception type: XlangSoapException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32,
Microsoft.XLANGs.Core.Context)
Help Link:
Additional error information:

Source: BizTalk Server 2004
Category: BizTalk Server 2004
Time: 10:45:12 AM
Type: Error
User: N/A
Event ID: 5752
The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due to
failures in message processing. Please refer to Health and Activity Tracking
tool for more detailed information on this failure.

Source: BizTalk Server 2004
Category: BizTalk Server 2004
Time: 10:45:11 AM
Type: Error
User: N/A
Event ID: 5754
The "SOAP" adapter is suspending an outbound message going to destination
URL:"http://localhost/InvokerCounter1/ServizioCounter1.asmx".
Details:"Operation Timeout".

I have check the suggestion link but not right help received.
I have increased the IIS timeout (600 seconds), the httpRuntime tag of
machine.config file (600 seconds), on the send ports of web services I have
tried to change the timeout, but I'm able to change only the Retry Count and
Retry Interval content.
In some documents I have read that another things is to set the property
value SOAP.ClientConnectionTimeout, but I haven't found it anywhere.
Can someone suggest me the stpes on how to increase send ports timeout?

Thanks,
Aniello.

[ Post a follow-up to this message ]

If you are calling a web service from an orchestration and need to increase
the timeout, you can do so by setting a context property on your outbound
message in a message assignment shape before sending.

MyMessage(SOAP.ClientConnectionTimeout) = 240;

Matt

"Aniello" <aniello> wrote in message
news:eJEiFaNkEHA.3724@TK2MSFTNGP11.phx.gbl...
>
>
> Hi all.
> I have an orchestration published as web service. Inside it there are two
> ports hooked on two web services that call an other orchestration
published
> as web service. This second orchestration runs for a long time (about 4
> minutes) for this reason I receive an exception in the first
orchestration,
> because the result doesn't come back in time. In the event viewer of
BizTalk
> I receive the subsequent errors:
>
> Source: XLANG/s
> Category: BizTalk Server 2004
> Time: 10:45:13 AM
> Type: Error
> User: N/A
> Event ID: 10034
> Uncaught exception terminated service
>
ComposedTransientCounter.ComplexScenario(a6019627-64ba-2309-2d47-11f9c08c5ec
> 6), instance 468a44fb-94f1-48ba-bd7f-e72235a71cd6
> An error occurred while processing the message, refer to the details
section
> for more information
> Exception type: XlangSoapException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32,
> Microsoft.XLANGs.Core.Context)
> Help Link:
> Additional error information:
>
> Source: BizTalk Server 2004
> Category: BizTalk Server 2004
> Time: 10:45:12 AM
> Type: Error
> User: N/A
> Event ID: 5752
> The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due
to
> failures in message processing. Please refer to Health and Activity
Tracking
> tool for more detailed information on this failure.
>
> Source: BizTalk Server 2004
> Category: BizTalk Server 2004
> Time: 10:45:11 AM
> Type: Error
> User: N/A
> Event ID: 5754
> The "SOAP" adapter is suspending an outbound message going to destination
> URL:"http://localhost/InvokerCounter1/ServizioCounter1.asmx".
> Details:"Operation Timeout".
>
> I have check the suggestion link but not right help received.
> I have increased the IIS timeout (600 seconds), the httpRuntime tag of
> machine.config file (600 seconds), on the send ports of web services I
have
> tried to change the timeout, but I'm able to change only the Retry Count
and
> Retry Interval content.
> In some documents I have read that another things is to set the property
> value SOAP.ClientConnectionTimeout, but I haven't found it anywhere.
> Can someone suggest me the stpes on how to increase send ports timeout?
>
> Thanks,
> Aniello.
>
>

[ Post a follow-up to this message ]

Hi Matt,
What is the default timeout setting?

Mangi.

"Matt Milner" wrote:

> If you are calling a web service from an orchestration and need to increas
e
> the timeout, you can do so by setting a context property on your outbound
> message in a message assignment shape before sending.
>
> MyMessage(SOAP.ClientConnectionTimeout) = 240;
>
> Matt
>
> "Aniello" <aniello> wrote in message
> news:eJEiFaNkEHA.3724@TK2MSFTNGP11.phx.gbl... 
> published 
> orchestration, 
> BizTalk 
> ComposedTransientCounter.ComplexScenario(a6019627-64ba-2309-2d47-11f9c08c5
ec 
> section 
> to 
> Tracking 
> have 
> and 
>
>
>

[ Post a follow-up to this message ]

The default for the SOAPHttpClientProtocol is 100000 milliseconds. I'm not
sure if the SOAP transmit adapter uses a different default to override this
or not, but I don't believe it does.  This works out to just over a minute
and a half.

matt


"Mangi" <Mangi@discussions.microsoft.com> wrote in message
news:A67EECC9-39DA-4ED3-ACEB-BEA9D25B2F4C@microsoft.com...[vbcol=seagreen]
> Hi Matt,
> What is the default timeout setting?
>
> Mangi.
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]

Hi Matt,
I have a script that looks like this in a message construct.

msgSkSetOrderRequest(SOAP.ClientConnectionTimeout) = 120;
msgSkSetOrderRequest(BTS.RetryCount) = 5;
msgSkSetOrderRequest(BTS.RetryInterval) = 1;

Is the RetryInterval in seconds or in minutes?
when i run it with the interval = 1, it retries every second for 5 seconds
then fails.

When i run it with the interval = 60, it reties after an hour.
I am baffled, i have absolutly no idea what is going on.
the message is going out on a dynamic port.

Mangi.

"Matt Milner" wrote:

> The default for the SOAPHttpClientProtocol is 100000 milliseconds. I'm not
> sure if the SOAP transmit adapter uses a different default to override thi
s
> or not, but I don't believe it does.  This works out to just over a minute
> and a half.
>
> matt
>
>
> "Mangi" <Mangi@discussions.microsoft.com> wrote in message
> news:A67EECC9-39DA-4ED3-ACEB-BEA9D25B2F4C@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]