Home/ Questions/Q 445669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T21:23:39+00:00

I have an orchestration that uses a request response port to call to a

  • 0

I have an orchestration that uses a request response port to call to a web service and wait for a response.
This is working perfectly.

I am now doing tests to handle errors and I am calling a web service that throws a divide by zero exception.
The orchestration doesn’t catch the exception as an exception; it acts as if the SOAP fault I am getting back is a regular string.

However when I tested this behavior with only a request port, I ended up within the catch block of the orchestration with the divide by zero exception.
I need to catch the web service exception also in the request response ports and not only on the one way port.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This type of error you are seeing is because there is a problem with the HTTP response coming from the web service. BizTalk tries to parse the received response and break it up into header and body and then parse the header. If the response is malformed HTTP, it causes this kind of error. It’s using the SOAP librbary to interpret the response message and it blows up becuase the message is bad. The divide by zero may happen because it couldn’t accurately get the response length form the header and then scrogged some math.

    I would place a packet sniffer on the line (like NetMon) and see what is actually being sent to BizTalk. If it’s not HTTP compliant (browse the spec or find a good HTTP for dummies), BizTalk can react un predictably.

    Best of luck.

    • 0