MAX cursor exceeded error after Migration from WAS4 to WAS5.1
Joined: Sep 23, 2003
I am facing error "Max cursor exceeded" in production environment.
The same application code was working well in WAS4, however, after migration to WAS5.1, the error started coming up every alternate day.
We have made it sure that all RS, STMT and connection objects ae closed in finally block.
To take preventive meausure, we are bouncing the server every night to reduce the cursor count to zero.
Details JDBC Provider class - oracle.jdbc.pool.OracleConnectionPoolDataSource oracle driver - classes12.zip oracle driver version - 184.108.40.206.0 URL = jdbc racle:thin:@wpshXXXX.win.XXXXXX.com:1521:wXX5 Minimum pool size = 10 Maximum pool size = 100 Connection time out = 180 s Idle time out = 1800 s Orphan time out = 1800 s Statement cache size = 1000 (for wepod instance) Disable Autoconnection cleanup = unchecked OPEN_CURSOR Parameter - 400
Any pointer towards solution is appreaciated!
Can anybody let me know how do I decide the value for parameter "Statement cache size" @ WAS side and OPEN_CURSOR @ DB side