Microsoft KB Archive/943125

= The XLANG Scheduler Engine enters an infinite loop, and a BizTalk Server 2006 process uses 100 percent of the CPU resources if a time-out exception is handled by a non-transactional scope =

Article ID: 943125

Article Last Modified on 12/13/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Standard Edition

-



SYMPTOMS
Consider the following scenario in Microsoft BizTalk Server 2006:
 * An orchestration contains a long-running scope in which the Timeout property has been set.
 * A non-transactional scope exists within the long-running scope. The non-transactional scope has a correlating receive shape.
 * The non-transactional scope also has an exception handler. This exception handler catches the Microsoft.XLANGs.BaseTypes.XLANGsException exception. This exception handler also starts another orchestration.

In this scenario, a BizTalk Server 2006 process may use 100 percent of the CPU resources if a time-out exception is handled by a non-transactional scope that is nested inside another long-running transaction scope.

If the correlating message is not received within the time-out value that is specified and if the TimeoutException exception is thrown, the Microsoft BizTalk Server XLANG Scheduler Engine enters an infinite loop. This causes 100 percent of the CPU resources to be used. Additionally, the start orchestration shape in the exception handler of the non-transactional scope will not be hit.



CAUSE
This problem occurs because the long-running transaction scope has special logic to handle time-out exceptions. However, the TimeoutException exception is not correctly handled by the non-transactional scope.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2006 service that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.



WORKAROUND
To work around this problem, set the inner non-transactional scope to be long running. For more information about how to make the orchestration a long-running transaction, visit the following Microsoft Developer Network Web site:

http://msdn2.microsoft.com/en-us/library/aa561340.aspx



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, visit the follow Microsoft Developer Network (MSDN) Web sites:

http://msdn2.microsoft.com/en-us/library/ms935411.aspx

http://msdn2.microsoft.com/en-us/library/aa995577.aspx

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: stuck

Keywords: kbfix kbhotfixserver kbqfe KB943125

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.