Microsoft KB Archive/321603

= BUG: Deadlock May Occur in the BizTalk Server Work Queue =

Article ID: 321603

Article Last Modified on 5/23/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition
 * Microsoft BizTalk Server 2000 Service Pack 1
 * Microsoft BizTalk Server 2000 Service Pack 1a
 * Microsoft BizTalk Server 2000 Service Pack 2
 * Microsoft BizTalk Server 2002 Standard Edition
 * Microsoft BizTalk Server 2002 Service Pack 1
 * Microsoft BizTalk Accelerator for RosettaNet 1.0 Enterprise Edition

-



This article was previously published under Q321603



SYMPTOMS
Work items in the BizTalk Server 2002 work queue may be marked for processing, but are not processed by a processing server. This may occur when the BizTalk Server is running in a moderate to high stress environment. If this occurs, it can cause a backlog of work items. No data is processed and no errors are logged in the Event log. This issue was discovered on the BizTalk Server Accelerator for RosettaNet.



STATUS
Microsoft has confirmed that this is a problem in BizTalk Accelerator for RosettaNet 1.0.



MORE INFORMATION
Although this problem was discovered in the BizTalk Server Accelerator for RosettaNet using Microsoft Visual Basic components, this may occur in BizTalk 2002 when a parent and child schedule both access the same port with the same method.

To avoid this problem, use the following best practices:
 * 1) Use separate ports.
 * 2) Use different method calls.
 * 3) Make sure that the different actions that are bound to the same port are called from the same schedule level.

NOTE: A loop structure in orchestration appears as a child schedule during run-time.

Keywords: kbbug KB321603

-

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

© Microsoft Corporation. All rights reserved.