Get BizTalk 2004 SP1 Installed!


If you haven’t already done so – please consider moving your development and live servers to BizTalk Server 2004 SP1 wherever possible.

It does really make a difference to common scenarios; it helped us out in the Scalability Lab recently with regard to SQL Server deadlocking under high load and also fixes a tricky bug whereby if your were using the SOAP adapter via dynamic ports you were prevented from moving the Adapter into another host to avoid the thread starvation problems.

It also introduced a few new handy performance counters as listed in the Readme (which we all read don’t we J), most notable are the new counters for the Messaging engine giving you a bit more “view” into the plumbing.

There’s plenty of other fixes listed here

Comments (2)

  1. Koen says:

    Hi Darren,
    <br>
    <br>what are the exact details about the SOAP adapter and the thread starvation problems??
    <br>
    <br>We have a problem with the SOAP adapter that sometimes the response message stays in HAT with status Dehydrated and we must remove the message manually. Can this be related?
    <br>
    <br>In very rare occasions, we have the SOAP adapter (running in a w3wp.exe process) generating the same response message over and over again and thus swamping BizTalk with messages. Could this be related too?
    <br>
    <br>Thanks,
    <br>Koen

Skip to main content