|
Home > Archive > BizTalk Server Orchestration > June 2004 > Orchestration exposed as web service
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Orchestration exposed as web service
|
|
|
| Hi,
I have exposed BizTalk Orchestration exposed as a web service. I have
exposed a SOAP Port. I am calling this exposed web service from an ASP.NET
web page. The page is able to send the request properly, and Orchestration
is returning results too properly. But still the control does not come back
to ASP.NET web page and hence raised operation time out exception. I dont
know how to debug this.
Any help would be highly appreciated.
--
Thanks & Regards,
Atul Shukla
| |
| Christof 2004-06-20, 11:09 pm |
| What do you mean with "return control" please?
Do you mean that the calling thread never returns? (timeout?)
You may change the settings of the WS proxy regarding the timeout if this is
the case...
Best regards,
Christof
"Atul" <pyaarey@hotmail.com> wrote in message
news:OuIYhWeVEHA.2700@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I have exposed BizTalk Orchestration exposed as a web service. I have
> exposed a SOAP Port. I am calling this exposed web service from an ASP.NET
> web page. The page is able to send the request properly, and Orchestration
> is returning results too properly. But still the control does not come
back
> to ASP.NET web page and hence raised operation time out exception. I dont
> know how to debug this.
>
> Any help would be highly appreciated.
>
>
> --
> Thanks & Regards,
> Atul Shukla
>
>
|
|
|
|
|