---
schema_version: "1"
id: 054fbea15248eacdacefb309de274a8d9328f5a67336a3224aa3a55796fc038e
title: Troubleshooting Cassandra Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cassandra-connector/4.1/cassandra-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/cassandra-connector/4.1/cassandra-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1ecda1b731e54915382cc37a7978449c13866071749bc74311fca52ed3ef66b2
description: MuleSoft Documentation Site
release: "4.1"
latest: false
---
---
product: Apache Cassandra Connector
version: 4.1
---

# Troubleshooting Cassandra Connector

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Apache Cassandra (Apache Cassandra Connector), become familiar with the information
about enabling verbose logging and interpreting commonly thrown messages.

## Enable Verbose Logging

To get a better understanding of why an application’s interaction with Cassandra Connector is
failing, temporarily enable verbose logging for the module.

Remember to always disable the enhanced verbosity after troubleshooting, because it affects your
Mule application performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` path folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name="org.mule.extension.cassandradb" level="DEBUG"/>
    				<AsyncLogger name="org.apache.commons.cassandradb" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Troubleshoot Prepared Statement Cache Size

If you receive the following warning message when running your Mule application:

---

WARN com.datastax.driver.core.Cluster \[Test-Cluster-worker-23\] Re-preparing already prepared query
is generally an anti-pattern and will likely affect performance. Consider preparing the statement
only once. ---

To avoid the previous message, increase the value of the **Prepared Statement Cache Size**
parameter, which enables you to set the cache size for prepared statements. Set a value with at
least the number of different statements that you handle in your Mule application.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [Known Issues](https://help.salesforce.com/s/issues)