I second.
You have to close your ResultSet, Statement and Connection
objects or all bets are off.
If you think you have problems now, try getting away with
this with a connection pool manager :-) (hint; You ruin
everyone else's day, too.)
kevin carothers [EMAIL PROTECTED]
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Summerfield
Sent: Thursday, January 27, 2000 9:07 AM
To: [EMAIL PROTECTED]
Subject: Re: Dr. Watson is attacking my computer
A couple of things I would change (which may or may not help though):
1) Call close() on result, statement and connection (in that order), after
you have finished with them - to make sure all resources used are freed up
immediately. Otherwise you'll find all available DB connections will get
eaten up in a short space of time.
2) You can safely place the the section that loads the JDBC driver into a
jspInit() method in the JSP - it only needs to be done once.
I have had a similar setups in the past give similar problems, though not
quite so extreme, however some work fine (different combinations/versions of
the various components?).
I do remember in one specific case that if I tried leaving the connection
open and re-using it across a number of requests, this did cause this
problem - opening/closing the connection each time fixed the problem, albeit
with the added overhead this entails.
Btw the JDBC-ODBC driver doesn't seem to have many fans...
HTH,
Steve S
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
