locked
BizTalk 2006 slows/stops processing RRS feed

  • Question

  • Normally my BizTalk server processes incoming files in under a second.  As such, the Work in Progress monitors normally display all 0's.  However, every 12 - 24 hours the Running service instances counter starts climbing.  CPU activity on the BizTalk server is at or near 0%.  At some point BizTalk stops picking up files from its receive locations.  After I restart the BizTalkServerApplication service, the queued service instances process in a few seconds.  How can I determine the source of this problem?

    I am running BizTalk 2006 R2 Enterprise.  SQL Server is running on a remote server.  All servers are adequately sized.  Orchestrations are used.  I have about 100 Receive Locations.  All Receive Locations reside on Windows shares.  Processed files end up in either a SQL Server database or a Windows share.

    Tuesday, April 7, 2009 8:35 PM

Answers

  • I would open up perfmon and look at the following items:
    BizTalk Messaging Agent

    Message Delivery Throttling State
    Message Publish Throttling State

    It probably at 4 or 6.

    Let us know...
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BillTheAdmin Friday, April 10, 2009 4:08 PM
    Tuesday, April 7, 2009 9:15 PM
  • I monitored the Message Publish Throttling State counters.  When BizTalk Running service instances started climbing, Message Publish Throttling State changed to a state of '4'.  The BizTalk Server is experiencing process memory pressure.

    I reduced the "Maximum number of messaging engine threads per CPU" in BizTalk Administrator from 20 to 10.  This seems to have resolved the issue.

    Open BizTalk Admin Console
    Expand BizTalk Group | Platform Settings | Hosts
    Right-click on BizTalkServerApplication | Properties | Advanced
    Change Maximum number of messaging engine threads per CPU setting
    Restart BizTalk Application service

    • Marked as answer by BillTheAdmin Friday, April 10, 2009 4:13 PM
    Friday, April 10, 2009 4:08 PM

All replies

  • Hi,

    I think you should start by monitoring both SQL Server and BizTalk server during normal and "high service instance" periods. Especially monitor for differences. You can do this by using the extensive set of performance counters that come with BizTalk, sql and windows.
    The PAL tool can be very helpful. see: www.codeplex.com/pal
     

    HTH,

    Randal van Splunteren
    http://biztalkmessages.vansplunteren.net

    Please mark answered if this answers your question.

    Tuesday, April 7, 2009 9:07 PM
    Moderator
  • I would open up perfmon and look at the following items:
    BizTalk Messaging Agent

    Message Delivery Throttling State
    Message Publish Throttling State

    It probably at 4 or 6.

    Let us know...
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BillTheAdmin Friday, April 10, 2009 4:08 PM
    Tuesday, April 7, 2009 9:15 PM
  • MsgBox Viewer is your friend (http://blogs.technet.com/jpierauc/pages/msgboxviewer.aspx). It will tell you if you're throttling, which may be the case. Since you are using FILE Receive Locations, you may also want to modify the MaxCmds and MaxMpxCt registry values documented in KB article 952566 - http://support.microsoft.com/?id=952556.
    Wednesday, April 8, 2009 5:56 PM
  • I monitored the Message Publish Throttling State counters.  When BizTalk Running service instances started climbing, Message Publish Throttling State changed to a state of '4'.  The BizTalk Server is experiencing process memory pressure.

    I reduced the "Maximum number of messaging engine threads per CPU" in BizTalk Administrator from 20 to 10.  This seems to have resolved the issue.

    Open BizTalk Admin Console
    Expand BizTalk Group | Platform Settings | Hosts
    Right-click on BizTalkServerApplication | Properties | Advanced
    Change Maximum number of messaging engine threads per CPU setting
    Restart BizTalk Application service

    • Marked as answer by BillTheAdmin Friday, April 10, 2009 4:13 PM
    Friday, April 10, 2009 4:08 PM
  • We had to change the MaxCmds and MaxMpxCt registry values for a slightly different issue long ago.  Specifically, Receive Functions would frequently disable themselves.

    MsgBox Viewer is provides a lot of good information about BizTalk and SQL Server configuration.  Thank you for the tool.
    Friday, April 10, 2009 4:11 PM