Hi Tobias, thanks for your response.
My problem is indeed similar to yours. The JDBC connection pool property I will go for is keepDynamic=1. In dependency to another parameter on the z/OS DB2 sub-system, this should bring us the prepared statement cache at Db2 (server) side. In previous releases of our software we also used prep statement, but only within transactions. JPA is re-using them over commits. With respect to resultSetHoldability=2, I saw in the attached link the this param should have value '1' for activation. What does '2' means here? ----- Kind regards Matthias -- View this message in context: http://openjpa.208410.n2.nabble.com/cursor-prepared-statement-problem-with-WebLogic-10-3-2-tp5724027p5769960.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
