PRB: Temporary Queues Are Stranded After the XLANG Scheduler Fails Over (312731)
The information in this article applies to:
- Microsoft BizTalk Server 2000
- Microsoft BizTalk Server 2002
This article was previously published under Q312731 SYMPTOMS
After a BizTalk Server cluster failover, sometimes the temporary private Microsoft Message Queuing queues that the XLANG Scheduler creates are not automatically deleted from the previously active node.
CAUSE
When BizTalk Messaging sends messages to an Orchestration schedule, the XLANGPort_1{GUID} schedule creates a temporary Message Queuing queue and messages are passed to this temporary queue and subsequently read from the XLANG Scheduler Engine.
After the BizTalk XLANG Scheduler Engine is configured as a clustered resource, Cluster Manager creates temporary Message Queuing queues on both configured nodes in the cluster so that in the event of a failover, these temporary queues are available on the node that is being failed over to.
If the BizTalk Service on the failing node is not shut down gracefully, BizTalk Server cannot clean up the temporary Message Queuing queues that the running XLANG schedule creates.
RESOLUTION
To resolve this behavior, manually delete the temporary Message Queuing queues that exist on the previously active.
STATUSThis behavior is by design.
| Modification Type: | Minor | Last Reviewed: | 1/4/2006 |
|---|
| Keywords: | kbnofix kbprb KB312731 |
|---|
|