Re: JSP JDBC bean doesn't seem to release cursor !?

[Keith Kwiatek]

so it does not open "just" one cursor per statement or result set ?   hmmm... BUT again, should it close the cursor when I issue the rs.close or stmt.close?   ----- Original Message ----- From: Panayotou, Michael To: [EMAIL PROTECTED] Sent: Tuesday, July 31, 2001 9:31 AM Subject: Re: JSP JDBC bean doesn't seem to release cursor !? A proper value for open_cursors is about 800 because Oracle uses a lot of recursive SQL statements in the server. -----Original Message----- From: Keith Kwiatek [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 31, 2001 3:03 PM To: [EMAIL PROTECTED] Subject: Re: JSP JDBC bean doesn't seem to release cursor !? My cursor limit is set to 200. I do not think raising the cursor limit is the problem.   Correct me if I am wrong, by I if a execute a result set close ( rs.close() ) and a statement close ( stmt.close() ) this should release the cursor. It should never get anywhere near the cursor limit. ??!!??   Keith       ----- Original Message ----- From: Zahid Rahman To: [EMAIL PROTECTED] Sent: Monday, July 30, 2001 4:44 PM Subject: Re: JSP JDBC bean doesn't seem to release cursor !? If memory serves me correctly   In the tnsnames file for oracle there is default cursor limit set to 50.   you need to increase the limit.   Zahid    ----- Original Message ----- From: Keith Kwiatek To: [EMAIL PROTECTED] Sent: Monday, July 30, 2001 9:32 PM Subject: JSP JDBC bean doesn't seem to release cursor !? Hello,   I am running oracle 8.1.6, and the 1.5.2 orion server.   I am using connection pooling.   I am using a JSP page with a jdbc java bean.   Everything works fine, except if I execute about 40-50 rapid executions of the JSP page, I run out of cursors.   I have rs.close, stmt.close commands at the end of each SQL call, BUT I see the cursor count climb with each execution.   The cursor count does go down with time, - I imagine the cursor times out. Also I notice that once the jsp page executes, I will not see the db connection close until a few minutes later, even though I have issued conn.close() explictedly (?) !   Can anyone give me some insight into what may be going on?   Keith