
Mule Debugger View Reference
This section contains a full description of the Mule Debugger View and all its available tools.
When the Mule Debugger starts, it points at the running Mule Runtime in Studio and waits for the Mule Event to reach its first active breakpoint.
Until then, the Mule Debugger View displays a placeholder message:

When the Mule Event stops at a Breakpoint, the Mule Debugger View displays information about the state of the Mule Event at that breakpoint:

Name | Description |
---|---|
Name column |
Displays the name of the Mule Event property |
Value column |
Displays the current value of the Mule Event Property |
Type column |
Displays the type of the Mule Event Property |
On the top right corner of the Mule Debugger View, you can find execution control tools for the Mule Debugger.
Icon | Name | Description | Shortcut |
---|---|---|---|
Mute Breakpoints |
Click to mute all the marked breakpoints. |
||
Terminate |
Click to stop the currently running application. |
||
Evaluate Mule Expression |
Click to evaluate a Mule expression. |
Linux and Windows: |
|
Next Processor |
Click to run the application and stop at the next Event Processor in the flow, even if there is no breakpoint at the next processor. |
|
|
Run to Processor |
Click to run the application and stop at the currently selected processor, even if there is no breakpoint at the currently selected processor. Emulates the behavior of the "Run to cursor" option in Java debuggers. (To select a processor, single-click its building block in the canvas.) |
|
|
Resume |
Click to run the application until the next breakpoint, if any. |
|
|
Start Scheduler |
When configuring a Scheduler in your Mule application, this option triggers the scheduler according to the frequency set in the poll scope. |
||
Stop Scheduler |
When configuring a Scheduler in your Mule application, this option it stops the initiated Scheduler. This function only works if the Scheduler has been initiated using the Start Scheduler button above. |