Tuesday, December 01, 2009

[BizTalk 2006 R2 Exception handling trick] #2 Catching the XLANGPipelineManagerException

Another item that is open for discussion is when to use a pipeline inside an orchestration. Whatever your opinion of using pipelines inside your orchestration is, please keep in mind that when any exception occurs in the pipeline, you want to catch the:

Microsoft.XLANGs.Pipeline.XLANGPipelineManagerException!

“Any failure in pipeline execution which would have resulted in a suspended message were this pipeline to be called from within the BizTalk Server Messaging Infrastructure will instead result in an exception being thrown. The exception thrown is of type Microsoft.XLANGs.Pipeline.XLANGPipelineManagerException. This thrown exception can be handled in a catch block within the calling orchestration. If the orchestration does not catch the thrown exception, the XLANGs engine reports an error the text of which includes the exception information in the thrown exception.”

Ref: http://msdn.microsoft.com/en-us/library/aa562035(BTS.10).aspx

No comments: