MuleSoft · Database Connector
Inconsistency!!! Statement culled from deathmarch
Short answer
This C3P0 error appears in Database Connector under high concurrency. The documented workaround is to set preparedStatementCacheSize to 0 on the pooling profile and set an Oracle JDBC statement cache size.
VerifiedLast verified
01Error text
java.lang.RuntimeException: Inconsistency!!! Statement culled from deathmarch failed to be removed by removeStatement(...)!02Likely causes
- The C3P0 connection pool's prepared statement cache fails under high concurrency.
03How to fix it
- Set
preparedStatementCacheSize="0"on<db:pooling-profile>. - Set the JVM parameter
-Doracle.jdbc.implicitStatementCacheSize=50. - Redeploy and repeat the load that triggered the error.
04Official documentation
→Related errors
- DB:QUERY_EXECUTIONDB:QUERY_EXECUTION means the database accepted the connection but the execution of the query failed. Turn on verbose logging for Database Connector to see the database's own message, then fix the query, its parameters or its timeout.
- DB:CONNECTIVITYDB:CONNECTIVITY covers several possible connection problems in Database Connector, including a poorly configured connection, no response from the database and a lost connection. Check the connection configuration first, then add a reconnection strategy.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer