QuestionQ22

MuleSoft application network concepts

An application deployed in a CloudHub production environment is throwing intermittent exceptions. To investigate the issue, a developer wants to enable DEBUG-level logging in production for the org.apache.cxf package in the deployed Mule application.

How should the developer update the logging configuration to enable package-specific debugging?

  • A In the Mule application’s log4j2.xml file, change the root logger’s level property to DEBUG, then redeploy the Mule application to the CloudHub production environment
  • B In Anypoint Runtime Manager, in the Deployed Application Properties tab for the Mule application, add a line item with DEBUG level for package org.apache.cxf and apply the changes
  • C In the Mule application’s log4j2.xml file, add an AsyncLogger element with name property set to org.apache.cxf and level set to DEBUG, then redeploy the Mule application in the CloudHub production environment
  • D In Anypoint Monitoring, define a logging search query with class property set to org.apache.cxf and level set to DEBUG
Explanation

Mule uses Log4j 2 and configures application logging through log4j2.xml. Package-level logging is enabled with an AsyncLogger whose name is the package and whose level is the desired severity. Setting org.apache.cxf to DEBUG enables detailed CXF logs without changing the root logger’s level; the updated application must be redeployed to CloudHub.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!