Orchestration Send Ports "Flooded" with single message endlessly repeated

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Orchestration Send Ports "Flooded" with single message endlessly repeated

Viewing 1 reply thread
  • Author
    Posts
    • March 25, 2009 at 8:07 PM #21979
      community-content

        Hi There.

        I have an orchestration with a single receive port (direct bound to MsgBox) and two send ports, binding set to later.  When the orchestration picks up the single message, it starts creating instance after instance of itself, generating endless messages at the send ports.

        What do I have to do to get only a single orchestration instance for the one message?  There is a filter on the Receive Shape that is specific to that one message.

        Thanks for the assist.

      • March 25, 2009 at 8:25 PM #21980
        community-content

          Soundslike you have created yourself a loop.
          A direct bound port without any additional filters will subscribe to any messages of the type specified on the activate receive shape.

          If you subsequently send the same message type out a send port, then another instance of the orchestration will begin, over and over.

          Are you sending the same message type out one of the send ports?

          • March 26, 2009 at 7:15 AM #21991
            community-content

              You are right.  One of the send ports archives the incoming message, so it outputs the original message to a folder with a File Adapter.

              Of course, now I have to figure out what other filter I would use on the receive shape to be sure it’s not subscribing to those archived messages.   That is a puzzle for me.  Any suggestions would be appreciated.

              Thanks.

              • March 26, 2009 at 12:03 PM #22001
                community-content

                  One suggestion, although I have never tried this is to change the message type of the archive message.

                  Declare an archive message within your orchestration of type System.Xml.XmlDocument (Untyped message) and assign this from the incoming message and send this to the archive port. 

                  What does the archive send port do? Is it just a passthru pipeline?

                  • March 26, 2009 at 9:01 PM #22018
                    community-content

                      I did read elsewhere a post about orchestration messaging and it confirmed your analysis. 

                      My activate receive shape did not have the MessageType as part of the filter, it was filtering on a promoted property – trying to filter on the MessageType just would not work.  However, I did follow your suggestion about Untyping the message and sending that out.

                      Also, the message coming in was xml, so I also changed the archive send port from PassThrough to XmlTransmit.

                      It now works!!!  Thank you very much, Greg.  Spot on with the observation and solution.[:D]

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