I recently opened a ticket with Microsoft due to a connectivity issue with a customer. The problem was ultimatly resolved by turning off the message chunking feature in the HTTP adapter configuration. It turns out that HTTP chunking is a HTTP 1.1 version feature and our customers servers still use HTTP 1.0.
While trying to resolve this issue the Microsoft technician asked me to add some XML to the BizTalk configuration file. The XML turns on the .Net Tracing feature that is built into the System.Net, System.Net.HttpListener, System.Net.Sockets and System.Net.Cache framework code. By adding the XML a file is generated in the same folder as the configuration file. The debug information can also be captured and viewed as it is generated using Debug Viewer by Sysinternals.
N.B. this was run with BizTalk 2006
XML
<configuration>
<system.diagnostics>
<trace autoflush="true" />
<sources>
<source name="System.Net">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.HttpListener">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.Sockets">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.Cache">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
</sources>
<sharedListeners>
<add
name="System.Net"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="System.Net.trace.log"
traceOutputOptions = "DateTime"
/>
</sharedListeners>
<switches>
<add name="System.Net" value="Verbose" />
<add name="System.Net.Sockets" value="Verbose" />
<add name="System.Net.Cache" value="Verbose" />
<add name="System.Net.HttpListener" value="Verbose" />
</switches>
</system.diagnostics>
</configuration>