|
|
Followup for anyone interested in the sql handle leak problem
I posted back in March:
Around the end of March, I posted a message describing a sql
handle leak problem we were seeing. At the time we were pretty sure it was
a problem with the sql cli layer in os/400. After working with IBM the
suggestion was made that maybe we were not closing all our statements/result
sets properly. Well I was willing to bet that we had carefully made sure
everything was good in our java code, but.... I did an audit myself of our
java code and found around 140 places where either the statement/result sets
werent closed or were not closed in the finally part of a try/catch/finally
block. Our programmers went through four iterations of auditing/changing
the code till we were finally satisfied.
The result: We have run over a whole week without
running out of handles as compared to running out within 24 hours prior to the
audit. If you are having any kind of handle leak problem, I suggest you
ignore your programmer's pleas of innocence and audit the code
carefully.
Suggestion to IBM: Give me a way to ask the system how
I'm doing on scarce resources like handles (green screen command, system api,
whatever). I know new releases dramatically increase the number of
available handles per job, but it would still be useful.
Alex Garrison
|
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
