---
schema_version: "1"
id: ca1475ed4198ef3912019cea958b61a50ac2fe722450104f4108eb0e0c5fb928
title: Troubleshooting JSON Module
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/json-module/latest/json-module-troubleshooting.md
canonical_url: https://docs.mulesoft.com/json-module/latest/json-module-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 43d89928009de47cbb513e81b248dea3920ba68150641cf9d5f90415010a2d4c
description: MuleSoft Documentation Site
release: "2.5"
latest: true
---
---
product: JSON Module
version: 2.5
is-latest-version: true
---

# Troubleshooting JSON Module

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

To troubleshoot JSON 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 the JSON 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.module.json" 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 an Invalid JSON Payload with Trailing Characters

The JSON module **Validate schema** operation now correctly detects an invalid JSON payload with
trailing characters.

To do so, you must add the system property `-DjsonSchemaValidator.FailOnTrailingTokens=true` to the
validation, as it is not a default behavior in the Jackson library used in the connector.

1.  In Studio, navigate to **Run > Run configurations…​**

2.  In the **Run Configurations** screen, select **Mule Applications** from the first column.

3.  Click the **(X)= Arguments** tab.

4.  In the **VM arguments** box, add the system property
    `-DjsonSchemaValidator.FailOnTrailingTokens=true`.

![The system property added in the VM arguments box](/mulesoft/current/en-us/json-module/latest/_images/json-system.png)

## Understand Common Throws

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

- JSON:INVALID\_INPUT\_JSON

  The input document is not valid JSON.

- JSON:INVALID\_SCHEMA

  The supplied schema is invalid.

- JSON:SCHEMA\_NOT\_FOUND

  The schema could not be found.

- JSON:SCHEMA\_NOT\_HONOURED

  The input JSON document does not adhere to its schema.

- JSON:SCHEMA\_INPUT\_ERROR

  The Validate schema operation failed because both the Schema and the SchemaContent fields were
  used at the same time during the operation's execution. You can only use one of these fields to
  validate schema XSD content.

## See Also

- [JSON Module Reference](https://docs.mulesoft.com/json-module/latest/json-reference)

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

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