≡ Menu




Generic fault message exception handling

 

In my current project, there are 50 operations on each port. It is very difficult and time consuming to create fault on every port operation and then add exception handler for every fault message.  This solution is not so comprehensive that if fault message is of different type what you made on each port

For example I selected “BTS.Soap_envelope_1__1.Fault on each operation,

than orchestration goes in suspended mode and process left uncompleted.

After too much search if found following exception type.

Microsoft.XLANGs.BaseTypes.UnexpectedMessageTypeException

 

Its works wonder if any fault message return my orchestration process is not break.

 

Pros: Normal exception caught and Orchestration completes its process.

Con: suspended instance of orchestration still visible at BizTalk admin with message “The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended.”

{ 0 comments… add one }

Leave a Comment