Oracle open cursors

[bazzac]

I have an application where the number of open cursors seems to increase over the day, and some times it does throw a "Too many open cursors" exception when it reaches the 300 limit. However, if it is left idle for 15 minutes the connections are closed.

I have checked that my code closes all Statements, PreparedStatements, ResultSets and Connections so I am not sure why the cursors are left open.

I am using JBoss 3.2.1 and finding it very difficult to find any documentation on how JBoss does Connection Pooling.

Thankyou
Carmen.

[cimetgiu]

I am using jboss 3.0.4 and I have the same problem....


please help!!!

[mharnvi]

Every time I have seen "To many open cursors", somewhere a Statement wasn't closed.

Try using finally-blocks to be shure they will be closed.

[jonlee]

A way to trap problems with unclosed statements is to migrate to JBoss 3.2.x. The connection pool management will flag messages when it detects unclosed statements when connections are returned to the pool.

[jonlee]

There have also been suggestions to increase the open cursor threshold in Oracle - this being with respect to other connection pool implementations.

[mblei]

I had the same problem and I fixed it by closing all Statements an ResultSets as soon as I finish using them as Yuleo says in the following thread: http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= wasted a lot of time trying different versions of jboss but the problem was in the code.