--- schema_version: "1" id: b4e2ae7de8d05e9f66a990ffc43edf41297bcfced22ead18c83467f2a20a6342 title: Mule Runtime Issues and Errors collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/troubleshoot-mule-runtime-errors.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-mule-runtime-errors source_site: docs.mulesoft.com content_type: documentation content_hash: 712fad5ade7595672fb66bd8387a7952f9775a674425389972db2acdfd14acaf description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # Mule Runtime Issues and Errors > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Code Builder includes bundled Mule runtime versions that enable instant project opening and design. When you run or debug applications, Anypoint Code Builder checks for the exact runtime version specified in your project. If the exact version isn’t available locally, error dialogs appear to help you resolve the issue. Don’t change the default locations of Mule. If you receive an error that Mule isn’t found or installed, configure the Mule Home path. When you configure Mule runtime, ensure you define the `mule.homeDirectory` property. > [!NOTE] The `mule.runtime.muleRuntimesDirectory` and `mule.runtime.muleHome` properties are legacy > configurations no longer used. - **Mule runtime versions**: The Mule runtime versions are located in the `{yourACBHome}/runtimes` directory. Default value: `/Users/{user}/AnypointCodeBuilder/runtime`. - **Mule Home**: The full path that points to the root files of the Mule instance. Default value: `/Users//AnypointCodeBuilder/runtime/` ## Mule Runtime Is Not Installed The error **Mule Runtime Is Not Installed, You Must Configure a Mule Runtime to Enable This Feature** occurs if **Mule Home** is misconfigured or empty and a feature requires a running Mule instance. For example, auto completion and debugging features require Mule to run. To troubleshoot this issue, use this procedure: 1. Locate the **Mule > Runtime: Mule Home** property: ![The Settings gear icon highlighted in the Anypoint Code Builder menu panel](/mulesoft/current/en-us/anypoint-code-builder/_images/open-settings.png) 2. Provide the full path to the folder that contains Mule runtime. This field must not be empty. ![Settings dialog showing Mule Home configuration field with default path](/mulesoft/current/en-us/anypoint-code-builder/_images/mule-runtimes-settings.png) ## No Mule Runtime Found The warning **No Mule runtime found. To perform this action, you must have Mule runtime configured.** occurs if: - Mule isn’t configured properly when you open Anypoint Code Builder - The **Mule Home** field is misconfigured or empty To troubleshoot this issue, use this procedure: 1. Go to your Anypoint Code Builder view, and select **Open ACB Settings**. ![The Settings gear icon highlighted in the Anypoint Code Builder menu panel](/mulesoft/current/en-us/anypoint-code-builder/_images/open-settings.png) 2. Locate the **Mule > Runtime: Mule Home** property: ![Settings dialog showing Mule Home configuration field with default path](/mulesoft/current/en-us/anypoint-code-builder/_images/mule-runtimes-settings.png) 3. Provide the full path to the folder that contains Mule runtime. This field must not be empty. ## Please Download and Install a JDK to Compile Your Project This request is _not_ from MuleSoft or Anypoint Code Builder: ![Notification showing a request to download and install a JDK to compile a project](/mulesoft/current/en-us/anypoint-code-builder/_images/troubleshoot-download-java-notification.png) For supported Mule workflows, Anypoint Code Builder resolves Java from the JDK packaged under your `AnypointCodeBuilder` directory. Using that local JDK source helps avoid machine-specific Java setup issues and improves project startup reliability. Instead of using this feature, you can use the command **Download Mule Runtime and Java Versions**. See [Version Settings for Mule, Java, and Connectors](https://docs.mulesoft.com/anypoint-code-builder/int-versions). ## Mule Runtime Version Not Defined The error **Mule runtime version not defined** occurs when your project doesn’t specify a Mule runtime version in the project’s `mule-artifact.json` file. To resolve this issue: 1. Click **Open Project Properties** in the error dialog, or run the command `MuleSoft: Open Mule Project Properties`. 2. In **Project Properties**, select a Mule runtime version. 3. Click **Apply**. ## Java Version Not Defined The error **Java version not defined** occurs when your project doesn’t specify a Java version in the project’s `mule-artifact.json` file. To resolve this issue: 1. Click **Open Project Properties** in the error dialog, or run the command `MuleSoft: Open Mule Project Properties`. 2. In **Project Properties**, select a Java version. 3. Click **Apply**. ## Mule Runtime Version Not Found (Compatible Version Available) The error **Mule runtime \[version\] not found** occurs when you try to run or debug an application, but the exact Mule runtime version specified in your project isn’t available locally. However, a compatible local version is available. To resolve this issue, you have two options: - **Continue with compatible version**: Click **Continue** to use the latest local compatible version. The dialog shows which version to use. - **Select a different version**: Click **Open Project Properties** to select a different local Mule runtime version or install the exact version using the `MuleSoft: Install Runtime` command. ## Mule Runtime Version Not Found (No Compatible Version) The error **Mule runtime \[version\] not found** occurs when you try to run or debug an application, but the exact Mule runtime version specified in your project isn’t available locally, and no compatible version is available. To resolve this issue: 1. Click **Open Project Properties** in the error dialog. 2. In **Project Properties**, either: - Select a locally available Mule runtime version from the dropdown, or - Use the `MuleSoft: Install Runtime` command to download the required version. 3. Click **Apply**. ## Java Version Not Found The error **Java \[version\] not found** occurs when you try to run or debug an application, but the Java version specified in your project isn’t available locally. To resolve this issue: 1. Click **Open Project Properties** in the error dialog. 2. In **Project Properties**, either: - Select Java 17 (or another available version) from the dropdown, or - Use the `MuleSoft: Download Mule Runtime and Java Versions` command to download the required Java version. 3. Click **Apply**. ## Mule Runtime and Java Version Not Found The error **Mule runtime \[version\] and Java \[version\] not found** occurs when you try to run or debug an application, but both the Mule runtime and Java versions specified in your project aren’t available locally. To resolve this issue: 1. Click **Open Project Properties** in the error dialog. 2. In **Project Properties**: - Select a locally available Mule runtime version and Java 17 (or another compatible version) from the dropdowns, or - Use the `MuleSoft: Install Runtime` command to download the required Mule runtime version, and use the `MuleSoft: Download Mule Runtime and Java Versions` command to download the required Java version. 3. Click **Apply**. ## Reinstall Mule Runtime If your Mule runtime installation becomes corrupted, you can force a reinstallation: 1. Close Anypoint Code Builder. 2. Navigate to your Mule runtime directory: `${user.home}/AnypointCodeBuilder/runtimes`. 3. Remove or rename the folder for the runtime version you want to reinstall (for example, `mule-4.6.0`). 4. Open Anypoint Code Builder. 5. Select the Mule runtime version from **Project Properties**. Anypoint Code Builder downloads and reinstalls the selected version. For details on selecting versions, see [Select Mule and Java Versions for a Project](https://docs.mulesoft.com/anypoint-code-builder/int-versions#project-version-mule-java). > [!NOTE] Your projects and other installed Mule runtime versions are not affected. ## See Also - [Known Issues](https://help.salesforce.com/s/issues)