Yep, thats right, you should close EVERYTHING as mentioned by Rajesh as in : > Rule - close everything
ResultSets, any (prepared/update)statements, connections (in case you are re-openning for any new query) should be closed in a finally block of your code where you use the above. The problem that you face is quite common with the above being left open at times. Just check up your code and make the relevant changes to ensure the above are closed. Regards, Ritesh ----- Original Message ----- From: "Thiharie Rajesh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 29, 2003 4:39 PM Subject: Re: odd oracle error > Database end > You need to increase the number of allowable > open cursors at the database end. Please lookup > your Oracle documentation to get to the right > point. > > Close ResultSets > This happens because you do not close ResultSets. > > Rule - close everything > Remember that the rule is to close every resource > you open. If you do not use connection pooling > be sure to close connections. > > Story / analogy > We ran into such problems when we did load > testing of an application at 250 simultaneous > users. Oracle does not clean out open anonymous > cursors for half-an-hour after they are opened. > > Cheers > Rajesh > > -----Original Message----- > at rare, random times we get the following error from our oracle 8i server > (8.1.7): > java.sql.SQLException: ORA-01000: maximum open cursors exceeded > > before anything I must say that we do close all our PreparedStatement, but > not the ResultSet. > AFAIK not closing the ResultSet shouldn't be a problem. We even had some > tests on this issue and they were successfull. > the maximum open cursors in our init.ora is 300 and we are using tomcat > 4.1.12 > > ____________________________________________________________________________ > ________________________ > > > This email and any attached to it are confidential and intended only for the > individual or > entity to which it is addressed. If you are not the intended recipient, > please let us know > by telephoning or emailing the sender. You should also delete the email and > any attachment > from your systems and should not copy the email or any attachment or > disclose their content > to any other person or entity. The views expressed here are not necessarily > those of > Churchill Insurance Group plc or its affiliates or subsidiaries. Thank you. > Churchill Insurance Group plc. Company Registration Number - 2280426. > England. > Registered Office: Churchill Court, Westmoreland Road, Bromley, Kent BR1 > 1DP. > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". > > Some relevant archives, FAQs and Forums on JSPs can be found at: > > http://java.sun.com/products/jsp > http://archives.java.sun.com/jsp-interest.html > http://forums.java.sun.com > http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
