DB2 - Problembeschreibung
Problem IC66104 | Status: Geschlossen |
COMMUNICATIONS ERROR MESSAGE '{1} IS NULL' FROM IBM DATA SERVER DRIVER FOR JDBC AND SQLJ, ON T4AGENT.SENDREQUEST() | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / 950 - DB2 | |
Problembeschreibung: | |
The following exception may be seen when using an IBM Data Server Driver for JDBC and SQLJ, Type 4 connection against a DB2 for z/OS subsystem, if the driver version is 3.57.82 (DB2 9.7 GA) or later: com.ibm.db2.jcc.am.yn: [jcc][t4][2030][11211][3.57.82] A communication error occurred during operations on the connection's underlying socket, socket input stream, or socket output stream. Error location: T4Agent.sendRequest(). Message: [jcc][t4][20121][11651]{1} is NULL.. ERRORCODE=-4499, SQLSTATE=08001 A JDBC trace capturing this error will show a tracepoint similar to the following, before the error is returned: [jcc][t4][time:2010-xx-xx-xx:xx:xx.xxx][Thread: <threadname>] [tracepoint:208]Null socketOutputStream in sendBytes, haveTransport_: true transportObject_: com.ibm.db2.jcc.t4.zb@2220222 transportKey_: NULL | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * JDBC applications connecting to DB2 for z/OS via Type 4 * * connection, using IBM Data Server Driver for JDBC and SQLJ * * version 3.57.82 or later * **************************************************************** * PROBLEM DESCRIPTION: * * The following exception may be seen when using an IBM Data * * Server Driver for JDBC and SQLJ, Type 4 connection against a * * DB2 for z/OS subsystem, if the driver version is 3.57.82 * * (DB2 9.5 Fix Pack 5) or previous : * * * * * * com.ibm.db2.jcc.am.yn: [jcc][t4][2030][11211][3.57.82] A * * * * communication error occurred during operations on the * * * * connection's underlying socket, socket input stream, or * * socket * * output stream. Error location: T4Agent.sendRequest(). * * Message: * * [jcc][t4][20121][11651]{1} is NULL.. ERRORCODE=-4499, * * * * SQLSTATE=08001 * * * * * * * * A JDBC trace capturing this error will show a tracepoint * * similar to the following, before the error is returned: * * * * * * * * [jcc][t4][time:2010-xx-xx-xx:xx:xx.xxx][Thread: * * <threadname>] * * [tracepoint:208]Null socketOutputStream in sendBytes, * * * * haveTransport_: true transportObject_: * * * * com.ibm.db2.jcc.t4.zb@2220222 transportKey_: NULL * * * * This exception is due to an issue with a timer which closes * * unused internal connections opened against DB2 for z/OS, * * when there is more than one active transaction on a single * * JDBC connection. This has been fixed in later versions of * * the JDBC driver. * **************************************************************** * RECOMMENDATION: * * Upgrade the JDBC driver to DB2 version 9.5 Fix Pack 6a or * * later. This is IBM Data Server Driver for JDBC and SQLJ * * versions 3.59.81 (JDBC 3.0 specification, db2jcc.jar) and * * 4.9.78 (JDBC 4.0 specification, db2jcc4.jar). * **************************************************************** | |
Local-Fix: | |
To circumvent this issue, create or modify a driver global properties file with the name 'DB2JccConfiguration.properties' and add the following line to it: db2.jcc.maxTransportObjectIdleTime=-1 Then place this file in a directory which is in the CLASSPATH. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in DB2 Version 9.5 Fix Pack 6a (IBM Data Server Driver for JDBC and SQL versions 3.59.81 and 4.9.78). | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.02.2010 13.05.2010 30.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6, 9.5.FP8, 9.7. | |
Problem behoben lt. FixList in der Version |