sql cli handle leaks followup -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.