Training Talks: What to do when debugger stops working in Anypoint Studio

training talks

Studio’s Visual Debugger allows you to run your application in Debug mode, stopping execution to check the contents of a message at previously-specified building blocks.

To do this, you set a breakpoint at any building block in your flow that you wish to check or test. When you run your application in Debug mode, the application stops immediately after executing the building block with the breakpoint. Using the Mule Debugger View, you can browse through the contents of the message as it exists at that point in the flow, and evaluate Mule Expressions against the message.

Training Talk – Episode 3

Let’s first review the steps you need to follow To start using the Visual Debugger in Anypoint Studio:

  1. Set Breakpoints breakpoints on building blocks in your application.
  2. Run in Debug Mode the application in Debug mode.
  3. View Message Data at a Breakpoint and/or Evaluate Mule Expressions the data in the first building block with a breakpoint.
  4. Resume application execution.
  5. Repeat step 3 with the next building block with a breakpoint, if any.

In this , Ethan will show us what to do when after setting a breakpoint, the flow is not stopping at the debugger, what are some possible causes and how to fix it.

Have questions for the Training team? Drop it in our forum or Training Twitter using the hashtag #TrainingTalks and stay tuned!

Our training modules are designed to help you learn how to be expert at using Anypoint Platform at any stage of development. To find out more about our role based recommended learning paths visit https://training.mulesoft.com/paths.


 


We'd love to hear your opinion on this post


One Response to “Training Talks: What to do when debugger stops working in Anypoint Studio”

  1. I have faced this issue so many times. This demo was very useful to understand how to work around this issue. Thank you, Ethan, for this demo.