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.

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 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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.

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:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, visit the follow Microsoft Developer Network (MSDN) Web sites:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: