Can someone further explain the platform specific FAQ on Oracle PreparedStatement Cache? I tried to google the issue, but I have not found anything. The FAQ is pasted below:
Quote:
After a while, Oracle throws this exception: too many open cursors
The Oracle JDBC driver doesn't much like to have its prepared statements cached. Disable PreparedStatement caching for the connection pool.
I have concerns about other side effects. Is this leaking memory on the Java heap or maybe even the C heap. Any help, be it an explanation or a link to an explanation, would be greatly appreciated.
Thanks in advance,
Kevin
Login
FAQ
Search