Subscription not available at this time…

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Subscription not available at this time…

Viewing 1 reply thread
  • Author
    Posts
    • October 22, 2008 at 6:13 AM #21035
      community-content

        Hi,

        I have an orchestration which just make the promotion of different properties and send the message in direct binding.

        No problem here.

        But
        sometimes the message sent falls in “routing failure” even if all the
        promoted properties needed to be routed to a specific orchestration are
        in the context.

        In the context of my sequencer, it’s possible i send many times the same message…

        For example :

        1. receive message A.
        2. receive message B
        3. Order message
        4. Send A.
        5. “Properties promotor” orchestration receive message A and 
          publishes this message for another orchestration with new properties in
          context.
        6. Receive functional error means i need to send message B before
          message A and after retry to send message A and message B in the goor
          order.
        7. Send B
        8. “Properties promotor” orchestration receive message B and  publishes
          this message for another orchestration with new properties in context.
        9. receive functional success
        10. (Re)Send message A
        11. “Properties promotor” orchestration receive message A and  add
          properties in the context and try to publishtis message => Routing
          failure

        Do you have any idea?

      • October 24, 2008 at 6:48 AM #21043
        community-content

          Are all of the properties promoted?  The properties need to be promoted to satisfy a subscription.  Setting the properties in an orchestration does not guarantee that they are promoted.  To promote the properties, you need to initialize a correlation set containing the properties on your send to the message box.

          • October 24, 2008 at 8:14 AM #21045
            community-content

              Thanksfor the reply.

              I investigated more… first, of course i initialize my correlation set, no problem… my properties are in the context and promoted.

              So, i found the problem, before sending my message, i log all the properties needed to be promoted. 3 properties :

              • CustomProperty1
              • CustomProperty2
              • BTS.MessageType

              All this properties have a value.

              But when i send my message I promote (initializing the correlation set)  the MessageType (i treat only xml document) and the property is empty even if i logged it in the previous Shape (and i saw the good value).

               

              When i use Orchestration Debugger and save the context of each message processed by my orchestration, the only difference is messageType is missing when the message falls in routing failure.

               

              I can’t explain it… sequencing messages using Biztalk is not easy!

               

              So i’m going on to search a solution…

               

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