Re: [OJB-developers] Open prepared statements

[Eric B. <EBi...@sa...>]

I was experiencing the same problem as you are until I started using OJB
version 0.7.343. If you're using OJB by putting jars on your classpath,
ensure that you've only got the specific jar you want to be using in your
classpath. Fyi, I'm using the ODMG interface against Oracle 8i, 8.1.6 using
the 'thin' oracle JDBC driver.

- Eric

----- Original Message -----
Subject: [OJB-developers] Open prepared statements
<snip>

When the database got built to around 100 E2 entities I started
getting errors thatthe available cursors had been exhausted.

Doing some investigation, I found that a prepared statement for
each E2 was being created, but they weren't being closed.  I put a quick
patch into ojb.broker.accesslayer.JdbcAccess to cache prepared statements,
and close them when the RsIterator is cleaning up.

This solves the immediate problem, but it isn't a long term fix.

Has this been experienced before?   Can I configure things differently so
I don't need the code change?

<snip>