CLOB.trim() causing Max cursors on SUNONE

Question

In a web application we are developing we call the trim( ) method on an oracle.sql.CLOB. When we deploy the application to Oc4J everything works just fine. If on the other hand we deploy the same application on A SUN ONE server, we run into a max cursor error. Analysis of v$open_cursor showed that for each time the clob.trim() method call is called there is an open cursor with the following SQL_TEXT
begin dbms_lob.trim (:1, :2); end;
In OC4J there is only one of these cursors per session
Both app servers use exactly the same JDBC drivers.
Both app servers connect to the same database.
Any ideas would be much appreciated

Answer 1

The trouble with that fix is that it only works if you want to immediately commit the transaction.
My approach to the problem was slightly different -- the bug seems to be in the Oracle drivers, so I simply don't call the Oracle trim method --
private void trimBLOB(Connection conn, Blob blob, int length) throws SQLException
CallableStatement stmt = null;
try
stmt = conn.prepareCall("{ call dbms_lob.trim (?, ?) }");
stmt.setBlob(1, blob);
stmt.setInt(2, length);
stmt.execute();
finally
stmt.close();