RE: jdbc handle leak problem solved

["Eyers, Daniel" <daniel.eyers@xxxxxxxxxxxxx>]

Nice job!!!  That sounds like a lot of work... 
 
thanks for the headsup!!!
 
dan
 

-----Original Message-----
From: Alex Garrison [mailto:agarrison@logtech.com]
Sent: Tuesday, May 30, 2000 3:25 PM
To: JAVA400-L@midrange.com
Subject: jdbc handle leak problem solved


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
 
  

+---
| 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
+---