Dehydrated Orchestrations BY THE THOUSANDS

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Dehydrated Orchestrations BY THE THOUSANDS

Viewing 1 reply thread
  • Author
    Posts
    • #22116

      OK, gurus, Here’s a good one for you.

      I have BT2006 (not R2) with HL7 accelerator 1.3 using HL7 2.3.1.We have a service that creates HL7 messages from a DB in XML format. This part is working great. 

      BT is configured to “watch” for these files in a folder and to get them, run them through a simple orchestration that maps the incoming XML to the HL7 messages and then sends them out via MLLP.We are processing in excess of 25,000 messages per day. When we first fire the service up, all is well.The XML service creates the message, BT grabs them, processes them and it goes through. 

      Everything looks good at this point. However, when we leave the services running, after about a day,when we re-check it, we have thousands of dehydrated messages (currently 28,000+) and BT has stopped pulling new messages in. Dehydrated messages are supposed to rehydrate when they can and continue on with whatever process they were in. These don’t seem to.

      The orchestrations (for each HL7 message type) are all almost exactly the same, receive port (for the XML), Receive shape, Construct Message Shape (for the mapping of the XML into the HL7 schemas), a Message Assignmnet Shape (to pull it all into the final message and create the MSH (HL7 Message Header)), then finally, a send shape matched to an MLLP send port.

      Any ideas on why these dehydrated orchs keep popping up? Am I missing something?

    • #22117

      I think we have a throttling scenario here – either message publishing or delivery throttling – as a result, the BizTalk engine is dehydrating your orchestrations in an attempts to resolve the throttling condition.

      Can I suggest that you review the MSDN Article at: http://msdn.microsoft.com/en-us/library/aa559893.aspx and let us know what the following performance counters are reporting:

      BizTalk: Message Agent: Message delivery throttling state

      BizTalk: Message Agent: Message publishing throttling state

      Rgds, Nick.

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