Troubleshooting Compression Module - Mule 4

To troubleshoot Compression 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 Compression 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/resources path folder.
Open the log4j2.xml file inside the folder.

Add an <AsyncLogger> tag inside the <Loggers> tag:

			<Loggers>
				...
				<AsyncLogger name="org.mule.extension.compression" level="DEBUG"/>
				<AsyncLogger name="org.apache.commons.compress" 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:

COMPRESSION:COULD_NOT_COMPRESS

An error occurred while trying to compress content.

COMPRESSION:COULD_NOT_DECOMPRESS

An error occurred while trying to decompress content.

COMPRESSION:INVALID_ARCHIVE

The content to decompress is an invalid archive.

COMPRESSION:TOO_MANY_ENTRIES

When an archive with multiple entries passes to the Decompress operation, the module is unable to choose only one entry.

Troubleshooting Compression Module - Mule 4

Enable Verbose Logging

Understand Common Throws

See Also