There was a known issue with weblogic severs and it was fixed with 6.0 release. The issue was that database resources are not been closed even if you close all JDBC objects.
-----Original Message----- From: Martin Kisimov [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 10:56 AM To: JDJList Subject: [jdjlist] RE: Maximum open cursor error Hi Vimal, Just a thought: Firstly your Oracle DB has a configuration file init.ora, which ahs a parameter which contains the number of maximum opened cursors. If you have many concurrent users logged on at the same time, accessing the DB at the same time, this may exceed your maximum opened cursors. If the setting in init.ora is small, even though you are closing the ResultSets, Statements and so on, this may result in the maximum cursors being reached. Otherwise if you are closing the appropriate objects straight after they are not required then I can't see any other problems. Hope this helps -----Original Message----- From: Sharma,Vimal [mailto:[EMAIL PROTECTED]] Sent: 11 July 2002 04:20 To: JDJList Subject: [jdjlist] Maximum open cursor error Guys, We have an application that runs Weblogic Server 6.1sp1 with Oracle Thin Driver on Oracle8.1.7. Servlet calls a stored procedure which returns a cursor, than fetches the rows using the cursor and then cleanly closes everything ( statements, results sets, connection ). Once in 3 days application cashes with Exception:ORA-01000: maximum open cursors exceeded. Mind it I have checked application many times for closing statement object, resultset object and connection object. Everything is closed. Can it be any other reason, like bug in oracle driver or in weblogic. If anybody has any clue on this, it will be greatly appreciated. Thanks, Vimal To change your membership options, refer to: http://www.sys-con.com/java/list.cfm
