BUG: XLANG May Leak ADO Connections When a Transaction Fails (817230)
The information in this article applies to:
- Microsoft BizTalk Server 2002, when used with:
- the operating system: Microsoft Windows 2000 SP3
- the operating system: Microsoft Windows 2000 SP2
- the operating system: Microsoft Windows 2000 SP1
- the operating system: Microsoft Windows 2000
SYMPTOMS A resource starvation issue may occur when you running multiple
XLANG schedule instances that fail with a 0x8004e007 error. This problem may cause the
database connection to be orphaned.
XLANG uses Microsoft ActiveX Data Objects (ADO) for database connectivity.
When this problem occurs, the database connection leaks may cause
multiple errors, including access violations. However, the error that occurs varies depending
on the application that is involved.This problem occurs under the following conditions: - The XLANG schedule instances that are running contain
transaction semantics.
- An ongoing transaction is aborted. This behavior causes an
error.
- The error causes COM Services to orphan the open connection to the XLANG
database, although XLANG closed the connection to the database correctly.
The
lack of system resources may cause an access violation in a custom
component. This problem may also cause an access violation in XLANG itself. Although this problem was found in
XLANG, this problem may occur in any application that uses ADO for database
connectivity and that is using transactions. STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 9/29/2003 |
|---|
| Keywords: | kbpending kbbug KB817230 kbAudDeveloper |
|---|
|