When you’re deploying and running a MuleSoft Mule Application in Anypoint Studio, it’s not immediately obvious where on your local machine it runs. Often this won’t matter, but when you are trying to build/deploy an application and the only error you get in the console is “check the logs”, maybe it’s time to find out where they live.
This happened to me when I received the following error (and very little else) when trying to deploy a simple application (you know the kind Mule support always ask for when you raise a support ticket?).
Failed to deploy artifact '<myApplication>', see +
artifact's log for details +
You might think the Mule Runtime would be under your AnypointStudio installation but this isn’t the case. Instead, Anypoint Studio executes a temporary instance of Mule Runtime which is located inside your user folders. On my Windows machine this is at
In the above folder, there are all the folders you’d expect to see associated with a Mule runtime – including a folder called logs. In this case, the <myApplication>.log file shows that my HTTP listener couldn’t bind to port 8081. It might have been nice to bubble this up to the main console, but at least I got there.