Using the BizTalk 2004 HTTP adapter with a trading partner that doesn't support HTTP Chunked Encoding (Introduced in HTTP 1.1)...

<< On Enlistment in BizTalk 2004 the WMI process is using more than the default memory quota of 128MB... | Home

Using the BizTalk 2004 HTTP adapter with a trading partner that doesn't support HTTP Chunked Encoding (Introduced in HTTP 1.1)...

I was working on a project where we needed to send messages from BizTalk to and HTTPS web page on a server that was running HTTP 1.0 and didn't support HTTP Chunked Encoding... http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html... The BizTalk 2004 HTTP adapter automatically chucks http posts into 48kb blocks, it has been discovered that when sending messages larger than 48kb to web servers that don't support chucking the following error will be raised in the event log - "The adapter failed to transmit message going to send port ““. It will be retransmitted after the retry interval specified for this Send Port. Details: "Chunked encoding upload is not supported on the HTTP/1.0 protocol."... Microsoft has recognised this problem and has created a hotfix “http://support.microsoft.com/default.aspx?scid=kb;EN-US;839663“ that enables you to disable HTTP chunking on a particular BizTalk host instance... I have applied this patch and it works well but again this highlights why it is a good idea to create a new BizTalk host for each BizTalk project ;)

Share This Post:

Print posted @ Saturday, October 16, 2004 3:44 AM

Feedback

# re: Using the BizTalk 2004 HTTP adapter with a trading partner that doesn't support HTTP Chunked Encoding (Introduced in HTTP 1.1)...

Thanks for putting this out there! I've burned a good part of my day today trying to figure out why my data wasn't making it to one of our packages. I had one doc that was 48kb and another that was 49kb, and the latter would never make it.

I'll have to look into this hotfix.

Thanks,
Curtis 6/23/2005 8:21 AM | Curtis Herrick

# re: Using the BizTalk 2004 HTTP adapter with a trading partner that doesn't support HTTP Chunked Encoding (Introduced in HTTP 1.1)...

This is also the error i'm receiving but after applying the registry values my HTTP post seems to complete successfully but my trading partner claims they are receiving nothing and the HAT is not tracking the outgoing messages (even thoug, inside the HAT configuration i have the default Microsoft send pipeline configured to track all outbound and inbound messages). Also the process is only taking about 19,000 ms to run. Where as before i disabled the chunked encoding the process took about 696,000 ms to process. MY XML document is 3,900 KB in size. 11/5/2005 4:54 AM | Julian

Nigel Parker