Configuring Mule Stacktraces
|Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.|
By default Mule filters out some internal class references from stacktraces to produce a more readable output. This behavior can be controlled one of three ways:
Setting properties in Mule Studio
Two command-line properties let you control this behavior using
mule.stacktrace.full- When present, Mule does not filter stacktraces. Intended for Mule developers only, end users probably never need to enable this. (You can also use the property
mule.verbose.exceptions=true, with the same result.)
mule.stacktrace.filter- A comma-separated list of packages and/or classes to remove from the stacktraces, which are matched via
In Studio, you can set the same properties specified above to instruct Mule to provide either unfiltered stacktraces or to configure a particular filter of packages or classes to remove. To adjust these settings:
Under the Package Explorer view open your
Define environment variables to specify the behavior you want.
In the example below, the
mule.stacktrace.full property is set to true.