|
Problem IC78529
|
Status: Closed |
CLIENT REROUTE MAY FAIL AND APPLICATION MAY RECEIVE SQL30081N IF HITTING COMMUNICATION ERROR AND CONNECTIONTIMEOUT IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Application connecting directly to a server may receive error
-30081 and following client reroute can fail. The problem can
happen if using db2dsdriver.cfg with ConnectionTimeout set and
enableWLB=true, and when initial connection handshake hits
communication error while receiving data.
Error received by application:
[IBM][CLI Driver] SQL30081N A communication error has been
detected. Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS". Location where the
error was detected: "1.2.3.4". Communication function detecting
the error: "selectForRecvTimeout". Protocol specific error
code(s): "0", "*", "*". SQLSTATE=08001
db2diag.log error entries:
2011-06-06-11.03.13.203000+000 LEVEL: Warning
PID : 1111 TID : 2222 PROC : xyz.exe
INSTANCE: NODE : 000
EDUID : 3333
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrRetrySetup,
probe:10
MESSAGE : ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT
"CONNECTION TIMED OUT"
DATA #1 : String, 30 bytes
Client Reroute is starting....
...
2011-06-03-11.03.13.250000+000 LEVEL: Warning
PID : 1111 TID : 2222 PROC : xyz.exe
INSTANCE: NODE : 000
EDUID : 3333
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrDrdaArShouldDoCR, probe:998
MESSAGE : ZRC=0x8037006D=-2143879059=SQLJR_CABLT "CA BUILT"
DATA #1 : String, 22 bytes
Client Reroute failed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.7 Fix Pack 4 and earlier clients on Linux, *
* Unix, and Windows platforms with ConnectionTimeout set *
****************************************************************
* PROBLEM DESCRIPTION: *
* Application connecting directly to a server may receive *
* error *
* -30081 and following client reroute can fail. The problem *
* can *
* happen if using db2dsdriver.cfg with ConnectionTimeout set *
* and *
* enableWLB=true, and when initial connection handshake hits *
* *
* communication error while receiving data. *
* *
* *
* *
* *
* *
* Error received by application: *
* *
* [IBM][CLI Driver] SQL30081N A communication error has been *
* *
* detected. Communication protocol being used: "TCP/IP". *
* *
* Communication API being used: "SOCKETS". Location where the *
* *
* error was detected: "1.2.3.4". Communication function *
* detecting *
* the error: "selectForRecvTimeout". Protocol specific error *
* *
* code(s): "0", "*", "*". SQLSTATE=08001 *
* *
* *
* *
* db2diag.log error entries: *
* *
* 2011-06-06-11.03.13.203000+000 LEVEL: Warning *
* *
* PID : 1111 TID : 2222 PROC : *
* xyz.exe *
* INSTANCE: NODE : 000 *
* *
* EDUID : 3333 *
* *
* FUNCTION: DB2 UDB, DRDA Application Requester, *
* sqljrRetrySetup, *
* probe:10 *
* *
* MESSAGE : ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT *
* *
* "CONNECTION TIMED OUT" *
* *
* DATA #1 : String, 30 bytes *
* *
* Client Reroute is starting.... *
* *
* *
* *
* ... *
* *
* *
* *
* 2011-06-03-11.03.13.250000+000 LEVEL: Warning *
* *
* PID : 1111 TID : 2222 PROC : *
* xyz.exe *
* INSTANCE: NODE : 000 *
* *
* EDUID : 3333 *
* *
* FUNCTION: DB2 UDB, DRDA Application Requester, *
* *
* sqljrDrdaArShouldDoCR, probe:998 *
* *
* MESSAGE : ZRC=0x8037006D=-2143879059=SQLJR_CABLT "CA BUILT" *
* *
* DATA #1 : String, 22 bytes *
* *
* Client Reroute failed. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5 or refer to Local Fix. *
**************************************************************** |
| Local Fix: |
Unset ConnectionTimeout |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.09.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
