|
Problem IT30972
|
Status: Closed |
JDBC DRIVER NOT TERMINATING TIMER THREADS WITH VERSION 11.5 GA (JCC 4.26.14)
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem description: |
Applications are getting large number of timer threads when API
timerLevelForQueryTimeout value is not set explicitly in an
application using JCC driver version JCC 4.26.14( Db2 version
11.5 GA) or later. The
number of threads grows continuously even though we are closing
all Connection objects. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5 M4 FP0(JCC 4.27.25) or later. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* 2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5 M4 FP0(JCC 4.27.25) or later. *
**************************************************************** |
| Comment |
Applications are getting large number of timer threads when API
timerLevelforQueryTimeout value is not set explicitly in an
application using JCC driver version 11.5 GA (JCC 4.26.14) or
later.
This issue is fixed in 11.5 M4 FP0(JCC 4.27.25). |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.11.2019
28.05.2020
22.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
