home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT01831 Status: Closed

DB2 CONNECT SERVER SENDS KEEP-ALIVE PROBES EVERY 5 SECONDS

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
DB2 CONNECT server may ignore the value for the following 
registry settings and use the default values: 
 
DB2TCP_CLIENT_KEEPALIVE_TIMEOUT 
DB2TCP_CLIENT_CONTIMEOUT 
DB2TCP_CLIENT_RCVTIMEOUT 
 
The APAR is only applicable if connection concentrator is 
enabled on DB2 CONNECT server.  The issue occurs if DB2 Connect 
server could not find a pooled agent to serve a new transaction 
for already connected application and creates  a new agent and 
new tcpip (socket) connection to the host server. Because of the 
APAR, new agent does not override the tcipip connection setting 
as per by registry value. Instead DB2 Connect server uses 
default value for the connection.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to v10.1fp5 or above                                  * 
****************************************************************
Local Fix:
Turn off the connection concentrator or use the direct client 
connection to the server.
Solution
First fixed in v10.1fp5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.05.2014
24.07.2015
24.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList