Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2005
    Posts
    1

    Unanswered: db2 connection timeout

    Hi,
    New to this board and a nube wrt to DB2.

    We're running into a scenario where the db 2 connection is timing out during reads.

    Is there a way to increase the timout value, somehow ?

    We get the following stack trace:

    com.ibm.db2.jcc.c.DisconnectException: A communication error has been
    detected. Communication protocol being used: Reply.fill(). Communication
    API being used: InputStream.read(). Location where the error was
    detected: Read timed out. Communication function detecting the error: *.
    Protocol specific error codes(s) TCP/IP SOCKETS
    at com.ibm.db2.jcc.b.a.a(a.java:424)
    at com.ibm.db2.jcc.b.bb.b(bb.java(Compiled Code))
    at com.ibm.db2.jcc.b.bb.c(bb.java(Inlined Compiled Code))
    at com.ibm.db2.jcc.b.bb.c(bb.java(Compiled Code))
    at com.ibm.db2.jcc.b.bb.v(bb.java(Inlined Compiled Code))
    at com.ibm.db2.jcc.b.eb.a(eb.java(Compiled Code))
    at com.ibm.db2.jcc.b.r.a(r.java(Inlined Compiled Code))
    at com.ibm.db2.jcc.b.ub.c(ub.java(Inlined Compiled Code))
    at com.ibm.db2.jcc.c.ad.Z(ad.java(Inlined Compiled Code))
    at com.ibm.db2.jcc.c.ad.d(ad.java(Compiled Code))
    at com.ibm.db2.jcc.c.ad.W(ad.java(Compiled Code))
    at com.ibm.db2.jcc.c.ad.execute(ad.java(Compiled Code))


    Any help would be appreciated.

    thanks.

    KHK

  2. #2
    Join Date
    Jan 2005
    Posts
    191
    Are there any messages in db2diag.log on either the client or the server? (It's location depends on the OS, eg under C:\program files\ibm\sqllib on a Windows system, ~instance-owner on a *ix system - but can vary.)

    I have a suspicion that this is really a comms problem - not a DB2 problem. You might need to, on your client, in a DB2 command environment
    db2 "update dbm cfg using diaglevel 4"
    rerun the error
    db2 "update dbm cfg using diaglevel 3"

    The db2diag.log might now show a SQLCA with sqlcode -30081. The tokens in the sqlerrmc field should give a better idea of the problem.

    http://www-1.ibm.com/support/docview...id=swg21164785
    may also help.

    James Campbell




    James Campbell

  3. #3
    Join Date
    Feb 2005
    Posts
    2

    diag messages

    I'm working with kirby on the same issue...
    We set the diagnostic level to 4 as you suggested and indeed started to see some comm errors. Any idea how to decipher these?

    005-02-13-14.56.52.442492-300 I11010204C452 LEVEL: Info
    PID : 786480 TID : 1 PROC : db2agent (ACH_PERF) 0
    INSTANCE: db28x32 NODE : 000 DB : ACH_PERF
    APPHDL : 0-63 APPID: GA01213F.P7A9.050213195631
    FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
    MESSAGE : CCI Error:
    DATA #1 : Hexdump, 4 bytes
    0x2FF13E48 : 0000 0036 ...6

    2005-02-13-14.56.52.442832-300 I11010657C437 LEVEL: Info
    PID : 786480 TID : 1 PROC : db2agent (ACH_PERF) 0
    INSTANCE: db28x32 NODE : 000 DB : ACH_PERF
    APPHDL : 0-63 APPID: GA01213F.P7A9.050213195631
    FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
    RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
    "External Comm error"

    2005-02-13-14.56.52.443174-300 I11011095C703 LEVEL: Info
    PID : 786480 TID : 1 PROC : db2agent (ACH_PERF) 0
    INSTANCE: db28x32 NODE : 000 DB : ACH_PERF
    APPHDL : 0-63 APPID: GA01213F.P7A9.050213195631
    FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
    DATA #1 : String, 333 bytes
    CALL STACK:
    [0] 0xD6C75714 sqljcReceive__FP10sqljCmnMgr + 0x238
    [1] 0xD6C77128 sqljsSqlam__FP7UCintfcP13sqle_agent_cbb + 0x228
    [2] 0xD6C775D8 sqljsDriveRequests__FP13sqle_agent_cbP11UCconHandl e + 0x8C
    [3] 0xD6C7747C sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0xB4
    [4] 0xD6C77250 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 0x88

  4. #4
    Join Date
    Feb 2005
    Posts
    2

    problem solved

    The problem was the type 4 JDBC driver.
    We were having deadlocks on the DB2 server side and the type 4 JDBC driver was throwing a SocketTimeoutException and closing the connection. When we switched to a type 2 driver it correctly reported the deadlock error and kept the connection alive.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •