Have seen this problem before. It is the JDBC code. The best solution is to explicitly close RESULTSET, STATEMENT (of any kind), and CONNECTION as soon as you finished using the object ( or else close them in the FINALLY block)
Regards, Michael -----Original Message----- From: Sean Dockery [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 1:04 PM To: Tomcat Users List Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF Try explicitly closing your ResultSet variables as well. See if the problem persists. At 13:58 2003-02-04, you wrote: >Configuring Tomcat to provide a JNDI connection pool was no problem. Now, >however, we are getting error ORA-01000: maximum cursors opened. Logging >shows that any statement and connection that is opened is again closed >which, according to everything I read, release the cursors. This is >obviously not the case. > >Has anyone else experienced this problem and, if so, what was the >resolution -- other than increasing opened cursor counts. > >Andy Meadows > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] Sean Dockery [EMAIL PROTECTED] Certified Java Web Component Developer Certified Delphi Programmer SBD Consultants http://www.sbdconsultants.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
