http://blogs.msdn.com/joncole/archive/tags/Soap/default.aspxTags: Soapen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/joncole/archive/2007/03/23/be-consistent-in-your-configuration.aspxFri, 23 Mar 2007 21:54:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:1938793joncole0http://blogs.msdn.com/joncole/comments/1938793.aspxhttp://blogs.msdn.com/joncole/commentrss.aspx?PostID=1938793<P>I recently worked with a customer using BizTalk 2004.&nbsp; They were experiencing some very odd behavior where a WebService client would call into a BizTalk WebService and experience a long wait before the client finally got a timeout error.&nbsp; The timeout happend to correspond to the 120 second timeout configured in IIS.&nbsp; </P> <P>Being fairly new to the Soap Receive Adapter code, I spent a couple hours looking over the code and some trace logs trying to understand what was happening.&nbsp; I finally noticed one very simple (yet easy to miss) mistake that the customer was making.&nbsp; They weren't being consistent in the configuration of the WebService.&nbsp; The Receive Port in BizTalk was configured as a Request-Response (two-way) port, as was the Web Method defined in the WSDL.&nbsp; However, within the WebMethod implementation, when&nbsp;they were calling the <EM>base.Invoke(...)</EM><STRONG> </STRONG>function on the ServiceProxy base class they were passing <EM>true</EM> for the <EM>oneway </EM>parameter.&nbsp;&nbsp;This inconsistency broke the contract between the WebService Implementation and the code that interacted with the Message Box, thus leading to the inconsistent behavior.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1938793" width="1" height="1">BizTalk AdaptersSoap