Troubleshooting JSON Module - Mule 4
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:
-
Access Anypoint Studio and navigate to the Package Explorer view.
-
Open your application’s project name.
-
Open the
src/main/resourcespath folder. -
Open the
log4j2.xmlfile inside the folder. -
Add an
<AsyncLogger>tag inside the<Loggers>tag:<Loggers> ... <AsyncLogger name="org.mule.module.json" level="DEBUG"/> ... </Loggers> -
Save your application changes.
-
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:
-
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.