|
Problem IC84401
|
Status: Closed |
DB2 WLM MAY NOT TERMINATE TRANSACTION ON UOW TOTAL TIME THRESHOL D VIOLATION IF APPLICATION IS WAITING FOR RESPONSE FROM CLIENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When WLM UOW total time threshold is defined, it is expected
that current transaction will be terminated as soon as
threshold time limit is reached. Agent working for the
application is responsible for checking if any of WLM threshold
limits are violated by the application.
However if coordinator agent for the application is waiting for
a new request to arrive from the fron-tend client, it is not
checking if UOW total time threshold limit is reached.
Therefore, in some cases, when we have "lazy client application"
it may be possible for a single transaction to last longer then
WLM limit defined.
To reproduce:
1. Create threshold:
CREATE THRESHOLD UOW1min FOR DATABASE ACTIVITIES
ENFORCEMENT DATABASE
WHEN UOWTOTALTIME > 1 MINUTE STOP EXECUTION;
ALTER THRESHOLD UOW1MIN ENABLE ;
2. Perform some activity and leave transaction open:
$ db2 connect to sample
$ db2 +c "create table t1 (c1 integer)"
$ db2 +c "insert into t1 values (1)"
$ sleep 180
Leave this tx open - do not run any other db2 commands from this
window.
3. From a different window, check if transaction is still open,
after 3 minutes:
$ db2 "select count(*) from t1 with UR"
You should see the data you inserted, rollback hasn't been done. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to DB2 Version 10.1.1 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 10 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
