0

I examined related questions here on this topic, and also googled for some time. Still seems I don't understand something crytical in Tomcat's DBCP configuration or mechanics.

I got Tomcat 6, DBCP resource configured in server.xml:

<Resource name="jdbc/myDB" auth="Container" description="Database connection"
  type="javax.sql.DataSource"
  driverClassName="com.mysql.jdbc.Driver"
  url="jdbc:mysql://myhost:3306/mydb?autoReconnectForPools=true&useUnicode=true"
  username="user"
  password="password"
  validationQuery="SELECT 1"
  testOnBorrow="true"
  testWhileIdle="true"
  timeBetweenEvictionRunsMillis="10000" minEvictableIdleTimeMillis="60000"
  maxActive="20" maxWait="20000" maxIdle="10"
  removeAbandoned="true" removeAbandonedTimeout="60" logAbandoned="true" />

Also I looked for mysql's wait_timeout and it is default 28800.

In summary I tried several options, but seems the problem is that mysql connections hit 28800 seconds of being idle and server closes them. I thought that pool should somehow handle this situation with validationQuery and testOnBorrow, but seems I'm wrong.

If I use autoReconnect in url after idle period My first query attempt results in "...CommunicationsException: The last packet successfully received from the server was 157,493,261 milliseconds ago." but after this it works normal.

If I use autoReconnectForPools in url or just don't use it - after idle period (8 hours) I got everytime ".MySQLNonTransientConnectionException: No operations allowed after connection closed".

In both cases things go smoothly while app has load. So, I concluded that connections was closed from side of mysql.

Help, what have I missed? I'd like to solve this problem without changing wait_timeout in Mysql. Goal - stable app which may survive idle times if it occur :)

dmitry
  • 4,989
  • 5
  • 48
  • 72
  • I may state that problem is namely in that fact that server closes connections after its timeout, but dbcp does nothing, no reconnect, no validation, no expiration from itself. – dmitry Jan 24 '13 at 13:47

2 Answers2

0

Not sure if it will help, but there's a newer (supposedly better) connection pool implementation in Tomcat 7.x - to use it, add this to your config:

factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"

I'm pretty sure that all of the rest of the options are the same. See http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html

GreyBeardedGeek
  • 29,460
  • 2
  • 47
  • 67
  • Thanks for information, though it is pretty uncertain will it solve my paticular problem or not :) – dmitry Jan 24 '13 at 13:49
  • I run in exactly this exception after upgrading from commons-dbcp connection pool to org.apache.tomcat.jdbc.pool – Ralph Jul 30 '13 at 07:10
0

I thought a bit, and decided to leave this question to be, though problem was not in Tomcat DBCP at all. My decision is motivated by the fact that I found quite a number of similar questions, and many of them unanswered, and never found a clue for what might have been going on. So, I leave a message here just as a warning for anyone suddenly walking the same path:

The problem was that I had a resource using database which was initialized just once, like:

class MyClass {
   private MyResource res = null;

   private MyResource getMyResource() {
      if (res == null) res = new MyResource(getConnection());
      return res;
   }

   private Connection getConnection() {
      ....
      con = dataSource.getConnection();
      ....
      return con;
   }
}

When my app was in Servlet it led to the situation where instance of MyResource were the only one, and had connection open. So, when MySQL server kill the expired connection my app would get exception about timeout on first query, but owing to autoReconnect for subsequent queries connection will be alive again. Pool just didn't touched connection because it had never been released.

Finally I realized it, and fixed by changing getMyResource to:

private MyResource getMyResource() {
  return new MyResource(getConnection());
}

In my case it was reasonable. After this change all things started to work as expected.

dmitry
  • 4,989
  • 5
  • 48
  • 72
  • Do return your connection to the pool after using it? Inorder to do that you must call connection.close() method. If your connection is not managed by pool it is going to be expired. – bhdrkn Feb 04 '13 at 12:18
  • I had written all I did and do now. I was mesleaded and treated my problems as related to DBCP, but it had ended up to be not. – dmitry Feb 04 '13 at 13:06