Re: sql cli handle leaks followup

[jom@xxxxxxxxxxxxxxx (Jacob Madsen)]

Hi Alex (or anybody, who has had a similar experience)

 

Thank you for sending the previous mail. You might be able to help me out of, what I see as a similar problem. I have a multithreaded Java server application running, which always after some random number of queries to the database crashes with this exception:

 

 

com.ibm.db2.jdbc.app.DB2SQLException2: SQL CLI (Call Level Interface) error
      com/ibm/db2/jdbc/app/DB2StatementRuntimeImpl.allocStmt(IIII)I+17(DB2StatementRuntimeImpl.java:74)
      com/ibm/db2/jdbc/app/DB2Statement.<init>(Lcom/ibm/db2/jdbc/app/DB2Connection;IIZ)V+315 (DB2Statement.java:248)
      com/ibm/db2/jdbc/app/DB2Connection.createStatement(II)Ljava/sql/Statement;+64 (DB2Connection.java:494)
      com/ibm/db2/jdbc/app/DB2Connection.createStatement()Ljava/sql/Statement;+19(DB2Connection.java:455)
      SQLInterface.createStatement()Ljava/sql/Statement;+4(SQLInterface.java:94)
      Iterator.<init>(Ljava/lang/String;)V+8 (Iterator.java:22)
      AccountR.<init>(Ljava/lang/String;)V+1 (AccountR.java:10)
      AccountR.findAccountID(Ljava/lang/String;)LKSProjekt/AccountR;+25(AccountR.java:45)
      Worker.getAccountInfo(Ljava/lang/String;)[Ljava/lang/Object;+5(Worker.java:460)
      Worker.inCash(LKSProjekt/InCasher;)V+93 (Worker.java:340)
      Worker.run()V+40 (Worker.java:41)
      java/lang/Thread.run()V+11 (Thread.java:466)
getSQLState() returned HY014

 

 

Does this sound familiar to you? I would appreciate, if you could re-send the information you mentioned in your previous mail, or if you could give me some hints on how to fix this crash.

 

Thanks in advance!

 

Jacob

----- Original Message -----

From: Alex Garrison

To: JAVA400-L@midrange.com

Sent: Tuesday, April 11, 2000 9:38 AM

Subject: sql cli handle leaks followup

Several weeks ago I posted some information indicating we were seeing continued handle leaks that eventually caused the native jdbc (sql cli) driver to stop working.  Our only solution at that time was to restart the websphere instance.

 

As a followup, several helpful folks at IBM (Richard D. and crew) helped us interpret the cli trace results.  Bottom line is that we still had some servlets that were not closing the statement objects in all cases - hence the slow leak of handles.  Although we had gone over this with all our developers months ago, a few hadnt made the necessary changes.  I just wanted to let everyone know that there does not seem to be any problem with the as/400 native jdbc driver/sql-cli handle management. 

 

Thanks again to the IBM'ers who took our problem seriously and helped out work it out.

 

Alex Garrison