---
schema_version: "1"
id: 16c0438d7510faa93013d1288109046c6d04f5b987ce1163030902eb2729a3b4
title: Troubleshooting Spring Module
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/spring-module/latest/spring-module-troubleshooting.md
canonical_url: https://docs.mulesoft.com/spring-module/latest/spring-module-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 026cc73ebde32e5abd119e7dfd4bec19e02f31f580887d66d617a5b4bed554e7
description: MuleSoft Documentation Site
release: "2.2"
latest: true
---
---
product: Spring Module
version: 2.2
is-latest-version: true
---

# Troubleshooting Spring Module

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

To troubleshoot Spring Module, 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 Spring module 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.spring" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

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

## Understand Common Throws

Here is a list of common throw messages and how to interpret them:

- MULE:NOT\_PERMITTED

  Occurs when there is a security restriction enforced by a filter; for example, when using the
  authorization filter of the Spring module.

- MULE:SERVER\_SECURITY

  Occurs when there is a security error enforced by Mule runtime engine (Mule).

## See Also

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

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