How to enable verbose / debug logging for the JMS connector

There are two options to achieve this, manually changing the log4j file in your mule application or through Anypoint Runtime Manager. The second approach is recommended when possible and it's the only alternative if you are deploying to CloudHub.

In Mule Runtime 3.x, you'll need to set DEBUG level to the following packages:

• org.mule.transport.jms
• com.mulesoft.mule.transport.jms

In Mule Runtime 4.x, you'll need to set DEBUG level to the following packages: 

• org.mule.extensions.jms
• org.mule.jms

1. Changing the log4j file

1.1. Modify the log4j2.xml file of your project (located on src/main/resources) and add the AsyncLogger tag containing the packages and level between the "Loggers" tag.

IE.

<Loggers>

    ...

    <AsyncLogger name="<package>" level="DEBUG"/>

    ...

</Loggers>

1.2. Replace <package> with the package required for your Mule Runtime version.

1.3. Save your project and deploy the new version.

2. Configuring it through the Anypoint Runtime Manager UI

2.1. Once in Runtime Manager select the application and go to "Settings".

2.2. Click on the "Logging" sub-tab, and on the menu below add the desired package with DEBUG level.

2.3. Apply changes.

IMPORTANT NOTE

Remember to always disable the enhanced verbosity after troubleshooting since it will affect your application's performance.