Most probably this is the problem with your database jobs or stored procedures, which are leaving the cursors around before exiting.
As I know, there is no such flag to say to tomcat. Another thing is, whether you are trying with load test, then that may be resonable. In that case, you can increase the open cursors in the database. Look at the following posting from oracle has lot of information. http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1041031921901 --- Hans Sowa <[EMAIL PROTECTED]> wrote: > Hi all > > I'm not sure if this is realy the right user list > for it but I try it. > My Problem is that I use connection pooling with > tomcat 5.0 and a oracle > database. My Problem is now I got the error message > "maximum open cursors > exceeded after a while. So I checked this and > actually I always close the > statement and the connection. I found out that it is > also a good approach to > close the result set. Ok, I also do this now but the > problem still exists. I > checked it with PL/SQL Client from that a lot of > cursors are still open > after closing. > > So, my question is, is there a flag to be set in > server.xml where I can say > please close all open cursor after connection > closing? > > Thanks in advance. > > -- > mfg Hans Sowa > mailto:[EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
