Topic
  • 7 replies
  • Latest Post - ‏2010-09-23T05:29:41Z by ndsampathkumar
SystemAdmin
SystemAdmin
17917 Posts

Pinned topic DB2 - Tomcat A communication error occurred

‏2008-09-30T05:25:12Z |
When Tomcat tries to create a DB2 connection it gets the follwoing error:

Caused by: com.ibm.db2.jcc.b.gm: jcct4203011211http://3.50.152 A communication error occurred during operations on the connection's underlying socket, socket input stream,
or socket output stream. Error location: Reply.fill(). Message: Connection reset. ERRORCODE=-4499, SQLSTATE=08001
at com.ibm.db2.jcc.b.wc.a(wc.java:283)
at com.ibm.db2.jcc.t4.a.a(a.java:352)
at com.ibm.db2.jcc.t4.ab.b(ab.java:200)
at com.ibm.db2.jcc.t4.b.<init>(b.java:298)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:193)

I would appreciate any information as to the cause of the problem and how to troubleshoot.
The port number where DB2 is listening is 50000

Thanks,
Vince
Updated on 2010-09-23T05:29:41Z at 2010-09-23T05:29:41Z by ndsampathkumar
  • SystemAdmin
    SystemAdmin
    17917 Posts

    Re: DB2 - Tomcat A communication error occurred

    ‏2008-11-22T02:42:25Z  
    Hello.

    I am wondering if you fixed that error. I get the same problems with Tomcat 6.0.14 and the DB2 Jdbc driver. Sometimes the db2 connection works, but sometimes it does not work.

    
    com.ibm.db2.jcc.b.gm: [jcc][t4][2030][11211][3.50.152] A communication error occurred during operations on the connection
    's underlying socket, socket input stream, or socket output stream.   Error location: Reply.fill().  Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
    


    If I tried to do the same things i need to do with jsp, using the same db2 connection class and only a java test class, everything works without problems. The problems are when I try to do it with Tomcat.

    If you fixed it, or not, I need help.

    Best regards.
  • SystemAdmin
    SystemAdmin
    17917 Posts

    Re: DB2 - Tomcat A communication error occurred

    ‏2009-01-27T14:09:25Z  
    Hello.

    I am wondering if you fixed that error. I get the same problems with Tomcat 6.0.14 and the DB2 Jdbc driver. Sometimes the db2 connection works, but sometimes it does not work.

    <pre class="jive-pre"> com.ibm.db2.jcc.b.gm: [jcc][t4][2030][11211][3.50.152] A communication error occurred during operations on the connection 's underlying socket, socket input stream, or socket output stream. Error location: Reply.fill(). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001 </pre>

    If I tried to do the same things i need to do with jsp, using the same db2 connection class and only a java test class, everything works without problems. The problems are when I try to do it with Tomcat.

    If you fixed it, or not, I need help.

    Best regards.
    Having the same issue here:

    com.ibm.db2.jcc.a.pm: A communication error occurred during operations on the connection's underlying socket, socket input stream,
    or socket output stream. Error location: Reply.fill(). Message: Connection reset. ERRORCODE=-4499, SQLSTATE=08001
    at com.ibm.db2.jcc.a.yc.a(yc.java:283)
    at com.ibm.db2.jcc.t4.a.a(a.java:352)
    at com.ibm.db2.jcc.t4.ab.b(ab.java:200)
    at com.ibm.db2.jcc.t4.ab.c(ab.java:237)
    at com.ibm.db2.jcc.t4.ab.c(ab.java:348)
    at com.ibm.db2.jcc.t4.ab.v(ab.java:1133)
    ...
  • SystemAdmin
    SystemAdmin
    17917 Posts

    Re: DB2 - Tomcat A communication error occurred

    ‏2009-09-09T21:38:37Z  
    Having the same issue here:

    com.ibm.db2.jcc.a.pm: A communication error occurred during operations on the connection's underlying socket, socket input stream,
    or socket output stream. Error location: Reply.fill(). Message: Connection reset. ERRORCODE=-4499, SQLSTATE=08001
    at com.ibm.db2.jcc.a.yc.a(yc.java:283)
    at com.ibm.db2.jcc.t4.a.a(a.java:352)
    at com.ibm.db2.jcc.t4.ab.b(ab.java:200)
    at com.ibm.db2.jcc.t4.ab.c(ab.java:237)
    at com.ibm.db2.jcc.t4.ab.c(ab.java:348)
    at com.ibm.db2.jcc.t4.ab.v(ab.java:1133)
    ...
    I found the solution at this site

    http://6by9.wordpress.com/
    June 18, 2009
    Tomcat/Jetty, DBCP, and Stale Connections
    Filed under: Uncategorized — agoodspeed @ 7:10 pm

    The underlying cause is that we sever all connections to the database for a nightly backup and the applications did not find out about it until they tried to run a query against a stale connection. As it happens though, Tomcat and Jetty (and probably many others) both use Apache Commons DBCP for connection pooling and there are configuration settings that can mitigate this problem; they are documented here – http://commons.apache.org/dbcp/configuration.html

    The settings we are trying in order to remedy the problem are:

    validationQuery="select 1 from sysibm.sysdummy1"
    testWhileIdle="true"
    timeBetweenEvictionRunsMillis="600000" We are also starting out with these settings which are not particularly related, but might be of interest to some.

    initialSize="4"
    maxActive="100"
    maxIdle="8"
    minIdle="2"
    maxWait="2000"
    removeAbandoned="true"
    logAbandoned="true"
  • tafranky
    tafranky
    1 Post

    Re: DB2 - Tomcat A communication error occurred

    ‏2010-05-28T00:47:45Z  
    I found the solution at this site

    http://6by9.wordpress.com/
    June 18, 2009
    Tomcat/Jetty, DBCP, and Stale Connections
    Filed under: Uncategorized — agoodspeed @ 7:10 pm

    The underlying cause is that we sever all connections to the database for a nightly backup and the applications did not find out about it until they tried to run a query against a stale connection. As it happens though, Tomcat and Jetty (and probably many others) both use Apache Commons DBCP for connection pooling and there are configuration settings that can mitigate this problem; they are documented here – http://commons.apache.org/dbcp/configuration.html

    The settings we are trying in order to remedy the problem are:

    validationQuery="select 1 from sysibm.sysdummy1"
    testWhileIdle="true"
    timeBetweenEvictionRunsMillis="600000" We are also starting out with these settings which are not particularly related, but might be of interest to some.

    initialSize="4"
    maxActive="100"
    maxIdle="8"
    minIdle="2"
    maxWait="2000"
    removeAbandoned="true"
    logAbandoned="true"
    I am facing the same type of issue using websphere pooling mechanism . Can anyone help.
    I am wondering if there is some setting in wehsphere that i can change in order to remedy this socket issue.

    Please helpo if you can .

    Error occurred.
    com.ibm.db2.jcc.b.gm: jcct4203011211http://3.50.152 A communication error occurred during operations on the connection's underlying socket, socket input stream,
    or socket output stream. Error location: Reply.fill(). Message: Connection reset. ERRORCODE=-4499, SQLSTATE=08001
    at com.ibm.db2.jcc.b.wc.a(wc.java:283)
  • facile27
    facile27
    1 Post

    Re: DB2 - Tomcat A communication error occurred

    ‏2010-07-19T14:48:20Z  
    Hi,

    I have the same error with websphere 6.1.0.31 and DB2.9.7 fix pack 2

    I would appreciate any information as to the cause of the problem and how to troubleshoot

    Thanks
  • SystemAdmin
    SystemAdmin
    17917 Posts

    Re: DB2 - Tomcat A communication error occurred

    ‏2010-09-01T08:16:42Z  
    • facile27
    • ‏2010-07-19T14:48:20Z
    Hi,

    I have the same error with websphere 6.1.0.31 and DB2.9.7 fix pack 2

    I would appreciate any information as to the cause of the problem and how to troubleshoot

    Thanks
    Hi ,

    We are facing the same issue with WAS 7.0 & DB2 9.7 during load test . Apprecaite your inputs to resolve the same.

    Thanks,
    Mansoor
  • ndsampathkumar
    ndsampathkumar
    1 Post

    Re: DB2 - Tomcat A communication error occurred

    ‏2010-09-23T05:29:41Z  
    Hi ,

    We are facing the same issue with WAS 7.0 & DB2 9.7 during load test . Apprecaite your inputs to resolve the same.

    Thanks,
    Mansoor
    Mansoor..

    Try this link.

    http://www-01.ibm.com/support/docview.wss?uid=swg1IC66104

    They have a workaround for the DB2 v 9.7 and above. I see this for DB2 v9.5.0.5 :(