3658998 - DB6: SQL30081N - Protocol specific error code(s): "238", "", " - Connecton Refused

ST22 - Short dump.

SQL30081N - A communication error has been detected.  Communication protocol being used: "TCP/IP".
LOG BYM=> sever DB error -99999; work process in reconnect status
hdl_error_on_commit_rollback: COMMIT/ROLLBACK failed due to lost connection.

Developer trace files:
A dev_w* file may contain errors like con_max is reached of 255.  This indicates that the number of requests is reached.

Example:
con_max = 255, con_opt = 255, occ = NO , prog =  
LOG BV4=> reconnect state is set for the work process
LOG BYY=> work process left reconnect status

Db2diag.log errors.

MESSAGE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
          "External Comm error"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -30081   sqlerrml: 39
sqlerrmc: 110 * * TCP/IP SOCKETS <IP_ADDRESS) recv 

"110" = ETIMEDOUT    -  A TCP timeout occurred while waiting for data.
"238" = ECONNRESET  -  he TCP connection was reset by the peer 

FUNCTION: DB2 UDB, data protection services, SQLPG_VENDOR_CB::sqlpVendorCallWrapper, probe:1000
DATA #1 : <preformatted>
Log manager is still waiting for a response from the vendor call. 

FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110
MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="111". (Connection refused" (ECONNREFUSED) 

Db2 LUW IBM

Network, layer, timeout, communication, API, SOCKETS, detected, "SelectForRecvTimeout", specific, protocol  , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem