|
Problem IT41270
|
Status: Closed |
ERRORCODE=-4474 RETURNED FROM JCC DRIVER FOR SET CURRENT PACKAGEPATH WHILE REUSING THE CONNECTION FROM THE POOL
|
| product: |
DB2 CONNECT / DB2CONNCT / B50 - DB2 |
| Problem description: |
When the application sets the currentPackagePath JCC property,
all connections in the connection pool uses the same CURRENT
PACKAGE PATH registry setting. Hence, setting this again on
subsequent connections that re-uses the connection from pool
results in -4474 error from jcc driver.
You may observe the following error:
com.ibm.db2.jcc.am.SqlException: [jcc][t4][1032][10352][4.28.11]
Cannot change current package path when pre-existing package
sets are in use on the connection. ERRORCODE=-4474,
SQLSTATE=null
at com.ibm.db2.jcc.am.b7.a(b7.java:794)
at com.ibm.db2.jcc.am.b7.a(b7.java:66)
at com.ibm.db2.jcc.am.b7.a(b7.java:133)
at
com.ibm.db2.jcc.am.Connection.setCurrentPackagePathX(Connection.
java:4135)
at
com.ibm.db2.jcc.am.Connection.setCurrentPackagePathX(Connection.
java:4123)
at com.ibm.db2.jcc.am.k6.a(k6.java:3119)
at com.ibm.db2.jcc.am.k6.c(k6.java:789)
at com.ibm.db2.jcc.am.k6.executeUpdate(k6.java:768)
Consider a following example scenario:
When using a HTTP request to execute transactions, it will apply
set the CURRENT PACKAGE PATH on all connections to the value set
for currentPackagePath property , and returns the connection to
the pool after completing the transaction.
When a subsequent connection request is made by application that
picks the connection from the pool, and if the application again
tries to set the CURRENT PACKAGE SET register either
programmatically or by overriding the currentPackagePath
property setting, the jcc driver throws -4470 error. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 JCC Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to JCC version for Db2 V11.5.8.0 or later *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2 JCC Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to JCC version for Db2 V11.5.8.0 or later *
**************************************************************** |
| Comment |
Problem fixed in Db2 V11.5.8.0. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.06.2022
07.10.2022
07.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
