Documents Are Left in the Work Queue When You Move Many Documents to the Suspended Queue at the Same Time (281182)
The information in this article applies to:
- Microsoft BizTalk Server 2000
This article was previously published under Q281182 SYMPTOMS
Under heavy loads, documents in the Work Queue are marked as in-process. When many documents are moved at the same time, documents are left in the Work Queue and marked as in-process instead of being moved to the Suspended Queue. There is no data loss and the server continues to process other incoming documents correctly.
CAUSE
BizTalk Server 2000 executes a stored procedure that checks to make sure that the number of rows that are moved to the suspended queue is 1, which should always be the case. If the value is anything other than 1, the stored procedure returns a false positive and does not move the document to the suspended queue. This problem is caused by a known issue with SQL Server, in relation to "NoLock," where the moved rows are set to a number greater than 1.
WORKAROUND
Manually move any documents that are left in the Work Queue to the Suspended Queue.
STATUSMicrosoft has confirmed that this is a problem in BizTalk Server 2000. MORE INFORMATION
When you move multiple documents to the Suspended Queue at the same time by using the cs_moveto_SuspendedQ_from_WorkQ stored procedure, some of the documents are left in the Work Queue, even though the stored procedure succeeds.
| Modification Type: | Major | Last Reviewed: | 10/17/2003 |
|---|
| Keywords: | kbbug kbpending KB281182 |
|---|
|