FIX: Documents May be Stranded in Private MSMQ Queues After Catastrophic Failure (824998)
The information in this article applies to:
- Microsoft BizTalk Server 2002
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSDocuments that are being sent from BizTalk Messaging to
BizTalk Orchestration can become stranded in the private MSMQ queue that
temporarily houses these documents in the event of a catastrophic failure such
as a power outage. When these documents are stranded in the private MSMQ
queues, they will remain stranded even after the BizTalk Server is restored to
working condition.CAUSEWhen you bind a BizTalk Messaging Port to an XLANG schedule,
the mechanism by which documents are passed to the schedule is referred to as
the Orchestration Activation Component (OAC). The OAC writes the document that
was being processed by the BizTalk Messaging engine to a private MSMQ queue,
and then instantiates the schedule that is bound to the Messaging Port. The
schedule in turn retrieves the document from the MSMQ queue. Once the schedule
picks up the document from the queue, the queue is deleted. If a catastrophic
failure occurs after the OAC writes the document to the MSMQ queue but before
the OAC instantiates the corresponding schedule, the document will become
stranded in the queue even after the server is restored.
This problem
can occur because the OAC does not persist a record of the process of writing a
document to the MSMQ queue. Therefore in the event of a failure, upon recovery
the OAC does not know that it is supposed to instantiate a schedule to pick up
any documents that it may have previously written to the MSMQ
queue.RESOLUTIONService Pack Information To resolve this problem, obtain the latest
service pack for Microsoft BizTalk Server 2002. For additional information,
click the following article number to view the article in the Microsoft
Knowledge Base: 815781 How to Obtain the Latest BizTalk Server 2002 Service Pack Hotfix Information To resolve this problem, obtain
the latest service pack for Microsoft BizTalk Server 2002. For additional
information, click the following article number to view the article in the
Microsoft Knowledge Base: 815781 INFO: How to Obtain the Latest BizTalk Server 2002 Service Pack
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was
first corrected in Microsoft BizTalk Server 2002 Service Pack
1.
Modification Type: | Major | Last Reviewed: | 7/31/2003 |
---|
Keywords: | kbfix KB824998 kbAudDeveloper |
---|
|