BAM does not completes the messages

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › BAM does not completes the messages

Viewing 0 reply threads
  • Author
    Posts
    • #24228

      Hi,

      We have a nightmare in the production environment where our solution for BizTalk 2006 (not R2) is deployed. It was reported that the number of monitored messages is about 5% less than the real number of messages was processed.  Although this happens only under stress conditions, each lost message is highly important. We’ve used TPE-based profile applied to the relatively simple orchestration: its activation Receive Shape is mapped to the first milestone in the profile and the last Send Shape is mapped to another milestone. That’s all. The matter was to measure the orchestration execution time and provide the summary about the total executed orchestrations. Now, when this orchestration is stressed, BAM records the events “selectively”: sometimes the first milestone is NULL and sometime the second one is NULL. These records remain in the active state forever in PIM database with NULL values. No event log, no TDDS performance counters, no Failed_TrackingData table are indicate the problem. We have the dedicated tracking host that does not go throttled during the stress.

      We are able to reproduce this behavior at the test environment, but I have no idea how to fix it.

      Any help be very appreciated.

      Thanks in advance.

       

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