This came up in a project that I recently worked. An orchestration in BizTalk was calling a long running/one way web service (i.e. fire and forget). Even though the web service didn't return anything, we were still getting timeout errors. Milton Perks did a bit of research and found this article on using the System.Web.Services.Protocols.SoapDocumentMethod(OneWay:=True) attribute on the web method. This solved the problem. Have a look at the original article for more details...
http://www.dotnetbips.com/displayarticle.aspx?id=271
posted on Monday, August 08, 2005 7:26 PM