Results 1 to 7 of 7
  1. #1
    Join Date
    Dec 2009
    Posts
    10

    Unanswered: SQL CODE 4499 on DB2 9.7 Patch 1

    Hi,
    I am working on DB2 9.7 Patch 1. I am running an SQL XML which fetches aroung 15 columns. One of these columns is of type CLOB. After fetching few records JBOSS gives the following error

    **ERROR**

    Message: jcct41037911961http://3.50.152 Client disconnect exception encountered: 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 ERRORCODE=-4499, SQLSTATE=null
    StackTrace: edu.wustl.query.util.querysuite.QueryModuleExcepti on: jcct41037911961http://3.50.152 Client disconnect exception encountered: 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 ERRORCODE=-4499, SQLSTATE=null
    at edu.wustl.cider.querymanager.CiderDataQueryExecuti onThread.processUPIResultSet(CiderDataQueryExecuti onThread.java:546)
    at edu.wustl.cider.querymanager.CiderDataQueryExecuti onThread****n(CiderDataQueryExecutionThread.java:3 64)
    at java.lang.Thread****n(Thread.java:595)
    Caused by: com.ibm.db2.jcc.b.hm: jcct41037911961http://3.50.152 Client disconnect exception encountered: 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 ERRORCODE=-4499, SQLSTATE=null
    at com.ibm.db2.jcc.b.wc.a(wc.java:281)
    at com.ibm.db2.jcc.b.wc.a(wc.java:301)
    at com.ibm.db2.jcc.t4.d.a(d.java:661)
    at com.ibm.db2.jcc.t4.d.b(d.java:722)
    at com.ibm.db2.jcc.t4.d.b(d.java:498)
    at com.ibm.db2.jcc.b.bc.a(bc.java:213)
    at com.ibm.db2.jcc.b.jk.c(jk.java:296)
    at com.ibm.db2.jcc.b.jk.next(jk.java:258)
    at org.jboss.resource.adapter.jdbc.WrappedResultSet.n ext(WrappedResultSet.java:1184)
    at edu.wustl.cider.querymanager.CiderDataQueryExecuti onThread.processResults(CiderDataQueryExecutionThr ead.java:169)
    at edu.wustl.cider.querymanager.CiderDataQueryExecuti onThread.executeDataQuery(CiderDataQueryExecutionT hread.java:131)
    at edu.wustl.cider.querymanager.CiderDataQueryExecuti onThread.processUPIResultSet(CiderDataQueryExecuti onThread.java:534)
    ... 2 more
    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.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)
    at com.ibm.db2.jcc.t4.eb.c(eb.java:30)
    at com.ibm.db2.jcc.t4.u.a(u.java:32)
    at com.ibm.db2.jcc.t4.j.Xb(j.java:245)
    at com.ibm.db2.jcc.b.jk.X(jk.java:3412)
    at com.ibm.db2.jcc.t4.d.a(d.java:658)
    ... 11 more
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream. java:168)
    at com.ibm.db2.jcc.t4.ab.b(ab.java:193)
    ... 19 more

    **ERROR**

    Can anyone provide me with a solution

    Regards
    Siddharth Shah

  2. #2
    Join Date
    Jan 2010
    Posts
    335
    Hi,

    i had to check the same error-message today, too.

    This is usally not a Problem with DB2, but a second instance of JBOSS running.

    Cheers

  3. #3
    Join Date
    Dec 2009
    Posts
    10
    Hi,
    I have only one instance of JBoss running on my machine

    Regards
    Siddharth Shah

  4. #4
    Join Date
    Jan 2010
    Posts
    335
    Hi,

    if you restart the JBOSS the old Java-Process might be still running.

    Was it working fine before?

    Check the Databases Manager Configuration?
    db2 get dbm cfg | grep "SVCE" (Unix)
    db2 get dbm cfg | find "SVCE" (Win)

    Which SVCENAME is given? If something like db2_DB2 is given, check the etc/services for the portnumber. Are you connecting to this port?

    Have you lately installed Fixpack 1? Did you run a rebind?

    Cheers

  5. #5
    Join Date
    Dec 2009
    Posts
    10
    Hi,
    I had checked before restarting the JBOSS whether old instance of java was still running and found out that no process of Java were running.

    Also the service name is db2c_db2inst1 and port number as 50000

    I have lately installed Fixpack 1 and have not ran a rebind

    Thanks
    Siddharth Shah

  6. #6
    Join Date
    Jan 2010
    Posts
    335
    After the Installation of a Fixpack you should do the following rebinds.

    Go to ~/sqllib/bnd
    db2 connect to <database>

    db2 "bind @db2cli.lst blocking all grant public"
    db2 "bind @db2ubind.lst blocking all grant public"
    db2 "bind db2schema.bnd blocking all grant public"

    Back to topic. Your settings look fine. I guess that DB2COMM=tcpip (db2set -all) is also set. So your DB2-Server should be fine.

    This might help or points the direction for your issue:
    How to solve Address or Port already in use error in java? | Digital Prank

  7. #7
    Join Date
    Dec 2009
    Posts
    10
    Hi,
    Thanks for all your help.

    However after doing a bind I am still facing the same issue.I also went through the link.

    Can one of the possibility be that I have limited the number of connections that java can make with DB2. Though I am not sure but its just a guess. However with the same configuration of my web.xml file I was able to run queries on number of tables with DB2 9.5 without any errors

Posting Permissions

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