Hi, we already have such a discussion on another thread, seems the tomcat-jdbc pooling can be the cause
using dbcp one as before can help (DataSourceCreator = dbcp in the datasource definition) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/4/4 Louis <[email protected]> > I'm working on migrating a project form Tomcat/OpenEJB to TomEE. > Everything > works great except for one piece of functionality. > > I have a scheduled import job that uses a long running user transaction > within a stateless session bean. Worked great for a couple of years now, > however it fails when ported to TomEE with the following: > > [PermanLawsonImportBean.java : 407] Actors Import > Failed.<openjpa-2.2.0-r422266:1244990 nonfatal general error> > org.apache.openjpa.persistence.PersistenceException: > org.apache.openjpa.lib.jdbc.ReportingSQLException: ORA-01000: maximum open > cursors exceeded > {prepstmnt 9556175 > > Again, running the exact same code against the exact same data set in > Tomcat/OpenEJB works fine. > > I tried increasing both the poolPreparedStatements and maxActive settings > and even had my DBA double the max open cursors. No luck. > > Besides rewriting/optimizing the current project, does anyone have any > ideas > as to what differences between the two environments (Tomcat/OpenEJB and > TomEE) could be causing this? > > Thanks, > Louis > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/org-apache-openjpa-lib-jdbc-ReportingSQLException-ORA-01000-maximum-open-cursors-exceeded-tp4661987.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
