Re: jdbc-IBM Connection Manager-Servlets and sql handles

> Do you see a downside to asking IBM to enhance the
> releaseIBMConnection() method to call Statement.close() on any open
> statements?

Yes! releaseIBMConnection() just puts the connection back in the pool-- the
connection is not necessarily closed at this point. It is very reasonable to
assume that some applicatoins might create a connection pool where
statements within the connections within the pool could be used more than
once. I am not sure how it would be implemented-- e.g., how would the second
user of a connection know that the statements have already been allocated?
One way might be to subclass the Connection and add some functionality for
application-specific statement management to the subclass, and let the pool
be instances of the subclass.. depending on the application at hand, this
could be a real performance booster.

Regarding the original problem of closing statements that will no longer be
used, be sure to do something like this:

// [statement opened]
try {
  // [use statement]
} finally {
  stmt.close();
}

to ensure that it will ALWAYS be closed no matter what might go wrong in
between..

Luther

> > Alex Garrison wrote:
> > We sent a sql cli trace to IBM and found out that we were running out
> > of free sql handles.  Long story short: You must call the
> > Statement.close() method when you are finished with a statement.  If


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---