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

MuleSoft error
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

  1. Set preparedStatementCacheSize="0" on <db:pooling-profile>.
  2. Set the JVM parameter -Doracle.jdbc.implicitStatementCacheSize=50.
  3. Redeploy and repeat the load that triggered the error.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.