Forcing a "Suspended (Non Resumable)" state

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Forcing a "Suspended (Non Resumable)" state

Viewing 2 reply threads
  • Author
    Posts
    • October 11, 2006 at 12:59 PM #16018
      community-content

        I'd appreciate any suggestion on this. I have an orchestration with its own retrying logic and error handling. For one specific message that is being sent on a dynamic send port, I need to mark the message as Non-Resumable in case the Send Port fails. I tried setting in the orchestration the BTS.SuspendAsNonResumable property of the message to true, but if the Send Port fails the message is still marked as being resumable. Is there some way to mark the message as non-resumable? Thanks
         

      • October 13, 2006 at 7:26 PM #16050
        community-content

          I don’t really know of a way. 

           

          That is kind of messing with the way BizTalk does recovery, guaranteed message, transmissions, etc.

           

          I know you can view the messages by status using WMI – but I don’t think you can change it.

           

          You could probably write some code inside your Orchestration exception block to terminate the message on the failed send port, but probably not change the state of the message.

           

          Hope this helps.

        • July 19, 2018 at 6:55 PM #41644
          Gabriel

            BTS.SuspendAsNonResumable property does’t work for me too? any suggestion?

            Thanks

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