BizTalk Exception: Calling web services with Mixed One-Way and Solicit-Response Operations

BizTalk Exception: Calling web services with Mixed One-Way and Solicit-Response Operations

 


There was a failure executing the response(receive) pipeline:

 "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler"

Send Port:

"ShippingMessageProcess_1.0.0.0_ShippingMessageProcess.ShippingMessageOrch_Port_ShippingWebServices_769f78805327fa55"

URI: "http://swsmis009/ShippingWebServicesApp/ShippingWebServicesApp.asmx"

Reason: The body part is NULL.

 

***

Generally, after deploying the project, a solicit-response send port will be created and bound to the orchestration. In this case, the above exception will occur when consuming the one-way web methods via a solicit-response physical web port.

 

You have to split the web services into two pieces, one web service only contains one-way web methods, and another web service only contains two-way (request / response) web methods. Then you can create two different ports in your orchestration and bind them to two different physical send ports, one that is one-way and one that is two-way.

 

 

 

 

posted @   Rickie  阅读(1219)  评论(1编辑  收藏  举报
编辑推荐:
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
· 理解Rust引用及其生命周期标识(上)
阅读排行:
· DeepSeek 开源周回顾「GitHub 热点速览」
· 物流快递公司核心技术能力-地址解析分单基础技术分享
· .NET 10首个预览版发布:重大改进与新特性概览!
· AI与.NET技术实操系列(二):开始使用ML.NET
· 单线程的Redis速度为什么快?
点击右上角即可分享
微信分享提示