Environment & Setup:
- System API (SAPI): Port 8081
- Process API (PAPI): Port 8083 (Calls SAPI via HTTP Request component)
Issue Description:
When running both APIs locally in debug mode, both applications deploy successfully. However, when PAPI sends an HTTP request to SAPI, execution does not trigger the breakpoints set in SAPI.
Troubleshooting Steps Taken:
- Reinstalled to the latest version of Anypoint Studio.
- Created a fresh workspace and re-imported the projects.
Khyati Mehta (InfinySkills) Forum Ambassador
Hello Abhijeet,
This usually happens because Anypoint Studio treats the two local APIs as separate applications/JVMs, so debugging PAPI doesn’t automatically attach the debugger to SAPI. Even though both apps are running in debug mode, the HTTP call from PAPI to localhost:8081 is just a normal HTTP request, and the SAPI debugger needs to be properly attached to the SAPI runtime for its breakpoints to trigger. I’d first check that SAPI is actually launched with Debug As - Mule Application, that the debugger is attached to the correct SAPI process, and that the breakpoint is placed on an executable Mule component rather than something that isn’t being executed. Also verify that PAPI is really calling
http://localhost:8081 and not another configured endpoint. If both projects are using the same workspace/runtime, restarting Studio and launching SAPI in debug first, then PAPI can also help. Hope this helps!
