Handling message delivery error in Send Pipelines

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Handling message delivery error in Send Pipelines

Viewing 2 reply threads
  • Author
    Posts
    • March 21, 2007 at 7:35 AM #18079
      community-content

        Hi,

        Does anyone suggest of any mechanism of handling any message delivery error ( for example destination folder does not exist) in the send pipeline or adapter so that the output message does not end up in the suspended queue?

      • March 21, 2007 at 1:32 PM #18085
        community-content

          you can use a secondary transport..(this can be specified while configuring a send port in biztalk admin) in case primary is not available it will use secondary and put a warning in the event viewer …now if secondary is also not available …that way message wont get suspended if that is what ur looking for..

        • March 21, 2007 at 3:02 PM #18089
          community-content

            Hi,

            There is a new great error-handling facility in BTS 2006 – Failed Message Routing.

            You can handle errors in send/receive port, adapters, pipeline, routing. It's simple and powerful. Find details in the  article on MSDN (link is here). I found another good sample of Failed Orchestration Routing in the Matt Meleski's blog. Both were very useful for me.

            Nick 

            • March 22, 2007 at 5:46 AM #18096
              community-content

                Thanks Nick,

                But what I wanted to achieve is that, when a send port or an adapter fails to send a message to the destination ( due to destination unavailability) after the stipulated retries the messages gets suspended. I dont want the message to get suspended. How can this be handled using custom pipelines or custom adapters?

                Naveen 

              • March 22, 2007 at 5:46 AM #18097
                community-content

                  Thanks Nick,

                  But what I want to achieve is that, when a send port or an adapter fails to send a message to the destination ( due to destination unavailability) after the stipulated retries the messages gets suspended. I dont want the message to get suspended. How can this be handled using custom pipelines or custom adapters?

                  Naveen 

                  • March 22, 2007 at 6:18 AM #18098
                    community-content

                      Yeah so you can use my solution, create a secondary transport which will always be available(a file folder on local can never be unavailable). Wonder why you have a requirement like that.

                    • March 22, 2007 at 3:31 PM #18110
                      community-content

                        Naveen,

                        If you mark "Enable routing for failed messages"
                        in your send port properties and a message occasionally failed to
                        deliver, it will not get suspended. Instead, BTS will create a
                        cloned message, add failure-specific properties and try to publish this
                        message. If publishing succeeds, BTS discard the original message.

                        So,
                        if your error handler subscribe this kind of messages and send them to
                        another port or wherever you will never have suspended messages for
                        that particular reason.

                        P.S. To enable routing for failed
                        messages use Administration console, not Visual Studio. And be sure to
                        subscribe error messages. 

                        Nick

                • Author
                  Posts
                Viewing 2 reply threads
                • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.