I am also not familiar with spy logs. I approached a colleague who is good at this and here is what his suggestions are:
1 - Quick workaround: Turn off WLS statement caching (set cache size to 0) 2 - Get latest version of the rebranded driver from Oracle. That may fix the problem, allowing statement caching again. If not, file a DD Driver bug with Oracle. This should be replicable outside openJPA with simple jdbc calls (calling same prepared statement twice). If you just repeat the exact same jdbc calls (that you see in spy logs), then you should be able to replicate the issue. The question is whether this happens *every time* a prepared statement for the same SQL is re-used. It is either a simple driver bug (where the cleanup JDBC code WLS do under the covers is messing up the DBMS's cursor state), or if there is some other application activity that messes up the DBMS (not as likely). -- View this message in context: http://openjpa.208410.n2.nabble.com/cursor-prepared-statement-problem-with-WebLogic-10-3-2-tp5724027p5767713.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
