Hi by default tomcat-jdbc but switching to DataSourceCreator=dbcp you will use dbcp (in datasource properties).
If you run both servers in parallel don't you have the same exceptions? (= can't be it some issues with MySQL at the moment) Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-07-18 16:43 GMT+02:00 Felipe Jaekel <fkjae...@gmail.com>: > Hi, > > After upgrading from 1.7.2 to 7.0.1 I saw some connection exceptions on the > log like this: > > com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications > link failure > > The last packet successfully received from the server was 35.540.502 > milliseconds ago. The last packet sent successfully to the server was 0 > milliseconds ago. > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at com.mysql.jdbc.Util.handleNewInstance(Util.java:404) > at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:988) > at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3552) > at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3452) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3893) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2549) > at > > com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861) > at > com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962) > at > > org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:70) > ... 39 more > Caused by: java.io.EOFException: Can not read response from server. > Expected to read 4 bytes, read 0 bytes before connection was unexpectedly > lost. > at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:3004) > at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3462) > ... 47 more > > It happened only six times, in a three minute interval, but since it didn't > happened with 1.7.2 I'd like to check. > > Database runs on the same server as TomEE, connection pool settings are the > same from 1.7.2: > > <Resource id="MySql" type="DataSource"> > > JtaManaged false > > JdbcDriver com.mysql.jdbc.Driver > > JdbcUrl jdbc:mysql://localhost/DB > > ConnectionProperties useUnicode=true;characterEncoding=UTF-8 > > UserName *** > > Password **** > > ValidationQuery select 1 > > TimeBetweenEvictionRunsMillis 30000 > > MinEvictableIdleTimeMillis 60000 > > MaxActive 100 > > </Resource> > > > Does TomEE uses The Tomcat JDBC Connection Pool or Commons DBCP? Do I need > additional pool config? > > Thanks >
