#87 NullPointerException in DoubleMaxStatementCache

[Miroslav Vidiscak]

I am getting this many times...

Environment: Java SDK 6.0.20, c3p0 v0.9.1.2
Database: MySQL Ver 14.14 Distrib 5.1.44-ndb-7.1.4b, for unknown-linux-gnu (x86_64) using readline 5.1 configured in cluster (2 instances of MySQL)
JDBC url: jdbc:mysql:loadbalance://x.y.z.w1,x.y.z.w2/db_name?loadBalanceStrategy=random&failOverReadOnly=false&autoReconnectForPools=true&roundRobinLoadBalance=true
c3p0 Properties:
maxIdleTime = 60
testConnectionOnCheckout = false
maxStatementsPerConnection = 100
maxStatements = 4000
idleConnectionTestPeriod = 55
maxPoolSize = 200
minPoolSize = 1
initialPoolSize = 5

Stacktrace:
Caused by: java.lang.NullPointerException
at com.mchange.v2.c3p0.stmt.DoubleMaxStatementCache.removeStatementFromDeathmarches(DoubleMaxStatementCache.java:59)
at com.mchange.v2.c3p0.stmt.GooGooStatementCache.removeStatement(GooGooStatementCache.java:482)
at com.mchange.v2.c3p0.stmt.GooGooStatementCache.access$200(GooGooStatementCache.java:40)
at com.mchange.v2.c3p0.stmt.GooGooStatementCache$Deathmarch.cullNext(GooGooStatementCache.java:701)
at com.mchange.v2.c3p0.stmt.DoubleMaxStatementCache.prepareAssimilateNewStatement(DoubleMaxStatementCache.java:68)
at com.mchange.v2.c3p0.stmt.GooGooStatementCache.checkoutStatement(GooGooStatementCache.java:170)
at com.mchange.v2.c3p0.impl.NewPooledConnection.checkoutStatement(NewPooledConnection.java:277)
at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:199)
at org.springframework.jdbc.core.JdbcTemplate$SimplePreparedStatementCreator.createPreparedStatement(JdbcTemplate.java:1362)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:580)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:811)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:867)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:875)

If you are missing something pls. write

Thx for answers&fixes

[Steve Waldman]

I believe this has been resolved (some time ago) as of 0.9.2_pre1.