|
Problem IC61699
|
Status: Closed |
TRANSACTION ABORTS AFTER CONNECTION LIFETIME PLUS 30 SECONDS DESPITE TRANSACTIONTIMEOUT IS SET TO A GREATER VALUE |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
When using the DB2 .NET Provider, a long running transaction is
aborted after Connection Lifetime plus 30 seconds despite
TransactionTimeout set to a greater value than Connection
Lifetime. Transactions should live until CommandTimeout or
TransactionTimeout is reached.
Example:
Connection Lifetime = 10
CommandTimeout = 60
TransactionTimeout = 60
A long running transaction aborts after 10 seconds plus 30
seconds (40 seconds) despite TransactionTimeout set to 60
seconds. The long running transaction should be aborted by the
TransactionTimeout, or at about 60 seconds. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* A TRANSACTION ABORTS AFTER CONNECTION LIFETIME PLUS 30 *
* SECONDS *
* DESPITE TRANSACTIONTIMEOUT IS SET TO A GREATER VALUE. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to IBM Data Server Provider for .Net 9.7 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
When using the DB2 .NET Provider, a long running transaction is
aborted after Connection Lifetime plus 30 seconds despite
TransactionTimeout set to a greater value than Connection
Lifetime. Transactions should live until CommandTimeout or
TransactionTimeout is reached.
Example:
Connection Lifetime = 10
CommandTimeout = 60
TransactionTimeout = 60
A long running transaction aborts after 10 seconds plus 30
seconds (40 seconds) despite TransactionTimeout set to 60
seconds. The long running transaction should be aborted by the
TransactionTimeout, or at about 60 seconds.
Problem was first fixed in Version 9.7 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.06.2009
19.01.2010
19.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
