Opened 12 years ago

Closed 12 years ago

#929 closed defect (fixed)

Run GeoNetwork with empty ORACLE database and ApacheDBCPool resource provider causes ORA-01000: maximum open cursors exceeded

Reported by: simonp Owned by: geonetwork-devel@…
Priority: major Milestone: v2.7.0
Component: General Version:
Keywords: Cc:

Description

Simon Pigot: Found that this was caused by Jeeves ApacheDBCPool resource provider using DBCP parameter maxOpenPreparedStatements which tries to cache the many sql statements that fill the empty GeoNetwork tables and consumes all available cursors in oracle db.

Problem will also occur if this DBCP parameter is used with Jeeves JNDIPool resource provider.

Fix is to allow the user to config this parameter in ApacheDBCPool (with default being off) and provide advice in docs that the prepared statement cache should not be config'd until after GeoNetwork database tables have been created and filled.

At some stage the database creation scripts used by GeoNetwork could be modified to use parameterized sql instead of many hundreds of individual sql statements.

Change History (2)

comment:1 by simonp, 12 years ago

Error was reported by ianwallen@… - thanks Ian!

comment:2 by simonp, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in svn revision 9180

Note: See TracTickets for help on using tickets.