Resuming failed messages, SOAP-adapter

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Resuming failed messages, SOAP-adapter

Viewing 1 reply thread
  • Author
    Posts
    • October 23, 2006 at 3:50 AM #16144
      community-content

        Hi,

        I have a problem resuming messages to a port using the SOAP-adapter. When I try to resume a message (which BizTalk characterizes as resumable), the message gets suspended again with the error description that no subscribers were found. When I look at the message context, the SPTransportID is promoted, and the value corresponds to the filter in the ports subscription. The port is in state Started.

        The orchestration that orriginates the messages uses exception handling and is terminated long before the messages are attempted resumed – there is nothing that subscribes to the response from the webservice call. If this is the cause of the problem, then how is it possible to handle the exception (and notify the calling party), and still be able to resend the soap message?

        Any help would be appreciated.

        Yours sincerely, Mads Lundemann.

      • October 23, 2006 at 7:26 PM #16169
        community-content

          Not really show the best way to accomplish this. 

           

          So your message that fails originates from the Orchestration?  If so, in this case I’d probably terminate the message and had logic to resend the whole request at a later time.

          • October 26, 2006 at 1:24 AM #16210
            community-content

              Thanks for your reply. 

              The messages originates outside BizTalk from a system, that calls BizTalk using an exposed web service. In BizTalk the orchestration is invoked and in turn invokes a web service with the original message to another system. It is imperative that the BizTalk web service responds to the calling system even if the other system isn't responding – however it would still sometimes be necessary to (after a user has analyzed the instance) resend the failed messages.

              I find it a little disturbing if it actually is necessary to make your own code for resending failed messages. BizTalk has logic for resending messages, and I really don't like spending time making something that should already be supported. If this scenario isn't supported by BizTalk, why are the messages marked as resumable? Also it would be preferable to be able to use the management console to resend the messages and not some custom interface (to keep the monitoring and management at one joint place).

              Regards, Mads.

              • October 26, 2006 at 9:15 PM #16217
                community-content

                  Well, if you were using a transport like File or MSMQ you would be able to resume the message and send it on.  The problem with SOAP is the receiver is not longer waiting to receive the message. 

                   

                  Not sure why the message is resumable.  Maybe in this case making them non- resumable would be better.

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