A few months back I posted about getting “canceled web requests” when calling a service on WebLogic from a BizTalk Server. Now, there appears to be a Microsoft hotfix that can address this.
While looking for another hotfix, I located this …
- Messages may be suspended when you use the HTTP adapter to send multiple messages to an Apache Web server, and the following error message may occur in BizTalk Server 2006: “Underlying connection was closed”
The cause given states “This problem occurs because you cannot set the HTTP header KeepAlive property to false when you use the HTTP adapter to send a message.”
There’s a non-hotfix workaround offered (which isn’t great), and then a description on how to set the “KeepAlive” to “false” after applying the hotfix. It’s a bit humorous, however, that the installation instructions include this little tidbit … “We do not recommend that you deploy this schema because future BizTalk Server updates may include an HTTP schema to set the KeepAlive property.” I’d prefer you not offer it as an option then! It’s recommended that you do NOT actually build out the property schema, but instead set the KeepAlive value in the pipeline.
Setting KeepAlive to false isn’t a great thing to do, but if you’re desperate, you now have a means to do it.
Technorati Tags: BizTalk
I have been intermittently getting this error in Biztalk
An error (The request was aborted: The request was canceled.) occurred while transmitting data over the HTTP channel. It only happens in my production environment. The web service that I have set up on the Biztalk Server 2006 R2, is calling an IBM web service on a Websphere server v6.1, that is a plug in generated for Content Manager 8.3 CMBSpecificWebService. At this point I am planning to use a custom binding to set KeepAliveEnabled=false.
What is the hotfix that you mention? What kind of errors will I see with KeepAlive disabled?
Hi Betty. The hotfix is here (http://support.microsoft.com/kb/924638/en-us). Not sure if you’ll see errors with KeepAlive disabled, but you just won’t be efficiently using connection pooling and may see a bit of service performance degradation.