aspose file tools*
The moose likes JDBC and the fly likes MAX cursor exceeded error after Migration from WAS4 to WAS5.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "MAX cursor exceeded error after Migration from WAS4 to WAS5.1" Watch "MAX cursor exceeded error after Migration from WAS4 to WAS5.1" New topic
Author

MAX cursor exceeded error after Migration from WAS4 to WAS5.1

Ashutsh Pitre
Greenhorn

Joined: Sep 23, 2003
Posts: 5
Hi ,

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 - 9.0.2.0.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

Thanks and regards,
Ashutosh
925 577 6482
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30758
    
156

Ashutosh,
For the statement cache size, you need to count up how many prepared statements you have. Note that this is the number of distinct SQL statements.

Then, keeping in mind that statements are not shared across connections, multiply that number by the connection pool size. That gives you the statement cache size.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Ashutsh Pitre
Greenhorn

Joined: Sep 23, 2003
Posts: 5
Hi Jeanne ,

Thanks for your reply. Can you plz let me know on what basis we dicide the max # of Pool zise for JDBC connectiion pooling in WAS5.1 ?

Thanks,
Ashutosh

Originally posted by Jeanne Boyarsky:
Ashutosh,
For the statement cache size, you need to count up how many prepared statements you have. Note that this is the number of distinct SQL statements.

Then, keeping in mind that statements are not shared across connections, multiply that number by the connection pool size. That gives you the statement cache size.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: MAX cursor exceeded error after Migration from WAS4 to WAS5.1