Hi Romain, I wanted to update you that we are seeing the same errors with the DataSourceCreator = dbcp. The only fix that works has been to revert to version 1.5.2.
Are there any significant differences in how 1.6.0 is handling DB connections? Can't upgrade until we resolve this. example msgs: bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: at com.cn.dsa.dovico.db.DbMgr.truncateTables(DbMgr.java:198) bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: at com.cn.dsa.dovico.db.DbMgr.truncateTables(DbMgr.java:198) bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: at com.cn.dsa.dovico.db.DbMgr.truncateTables(DbMgr.java:198) bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: at com.cn.dsa.dovico.db.DbMgr.truncateTables(DbMgr.java:198) bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: at com.cn.dsa.dovico.db.DbMgr.truncateTables(DbMgr.java:198) bombed truncating table: MAILINGS_DETAIL, No more data to read from socket bombed truncating table: MAILINGS_DETAIL, No more data to read from socket bombed truncating table: MAILINGS_DETAIL, No more data to read from socket miles Miles Poindexter Service Oriented Architecture [email protected]<mailto:[email protected]> 347-967-8944 / 212-790-6692 On Feb 7, 2014, at 10:58 AM, Romain Manni-Bucau <[email protected]<mailto:[email protected]>> wrote: yep Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-02-07 Poindexter, Miles <[email protected]<mailto:[email protected]>>: Thanks! I will try that today if not Monday. I guess the default is: DataSourceCreator = tomcat ? Miles Poindexter Service Oriented Architecture [email protected]<mailto:[email protected]><mailto:[email protected]> 347-967-8944 / 212-790-6692 On Feb 7, 2014, at 10:43 AM, Romain Manni-Bucau <[email protected]<mailto:[email protected]><mailto:[email protected]>> wrote: hi maybe try to use dbcp: DataSourceCreateor = dbcp Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-02-07 Poindexter, Miles <[email protected]<mailto:[email protected]><mailto:[email protected]>>: Hi, I'm investigating problems with our database connections after upgrading from TomEE 1.5.2 to 1.6.0 After the upgrade, we starting getting a lot of "Connection to DB closed" type error messages. And operations like table truncating are failing. I have reverted our production platform to 1.5.2 to see if this fixes the issue, and will let you know if it disappears. Example log messages: bombed truncating tables: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: bombed truncating table: MAILINGS_DETAIL, No more data to read from socket I never saw these type of errors before the upgrade. Has anyone else had problems like this? This is happening on TomEE 1.6.0 running on Redhat 5. Problems are happening with both Oracle and MySQL. Drivers added to [TOMEE_HOME]/lib/: mysql-connector-java-5.1.6.jar ojdbc6.jar (for Oracle) Would a driver update possibly fix this? miles Miles Poindexter Service Oriented Architecture [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> 347-967-8944 / 212-790-6692
