JOTM, XAPool, and Oracle

[dp3]

I'm getting a "maximum open cursors exceeded" error when using JOTM, XAPool, and Oracle. I recently went from DBCP to JOTM/XAPool and never had that problem when using DBCP. When I set the "preparedStmtCacheSize" of StandardXADataSource to 0, the error isn't present (so that's the likely culprit).

I just wondered if anyone else had this problem and if there is a way to keep a preparedstmt cache and avoid the cursor error.

Also, it appears that outside of using a J2EE container, JOTM/XAPool is the way to go for distributed transactions. Is there anything else recommended?

Thanks
~D

[Rod Johnson]

I've seen open cursors exceeded with Hibernate/Commons DBCP, even with local transactions. The issue seems to be the Oracle thin driver and prepared statement caching, rather than the transaction management.