Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.7.11
-
None
-
None
Description
There is some evidence that cache should be larger (see below) but there's no way to alter this setting because it's set programmatically – see http://www.mchange.com/projects/c3p0/#configuration_precedence
btpool0-316: RUNNABLE java.util.TreeMap.deleteEntry(TreeMap.java:2146) java.util.TreeMap.remove(TreeMap.java:585) com.mchange.v2.c3p0.stmt.GooGooStatementCache$Deathmarch.undeathmarchStatement(GooGooStatementCache.java:678) com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache.removeStatementFromDeathmarches(GlobalMaxOnlyStatementCache.java:50) com.mchange.v2.c3p0.stmt.GooGooStatementCache.checkoutStatement(GooGooStatementCache.java:188) com.mchange.v2.c3p0.impl.NewPooledConnection.checkoutStatement(NewPooledConnection.java:277) com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:199) <...>
Attachments
Issue Links
- duplicates
-
FE-3969 The 'Parameters' on the 'Database Configuration' page are ignored.
- Closed