Anypoint Studio 6.4 with Mule Runtime Engine 3.9.0 Release Notes

October 6, 2017
Build ID: 201710062112


Mule Runtime

Version: 3.9.0 EE

Anypoint Studio

Version: 6.4
Build Id: 201710062112


Versions: 3.8.1 - 3.8.0 - 1.7.3 - 1.6.2 - 1.5.3


Version: 1.2.0


Version: 1.6.0 (munit-studio-plugin)

SAP Connector

Versions: 3.2.0

What’s New

This release of Studio 6.4.0 includes mainly bug fixes and improvements including:

  • Mule Runtime 3.9 support (bundled).

  • CRL support for TLS configurations (from Mule Runtime 3.9).

  • Proxy configuration for SFTP (from Mule Runtime 3.9).

  • Fixes for debugger when using scatter-gather, breakpoints, parallel, requests and handling exceptions.

Hardware Requirements

  • MuleSoft recommends a minimum of 4GB RAM on a developer workstation. As applications become complex, consider adding more RAM.

  • 2GHz CPU

  • 10GB free hard drive space

Software Requirements

Java Environments

  • Oracle JDK 1.8.0
    This version of Anypoint Studio requires Java 7 or Java 8 depending on which Mule runtime you want to use:

  • Mule 3.9.x requires Studio running on Java 8.

  • Mule 3.5.x requires Studio running on Java 7.

  • Other supported runtime versions work fine with both Java 7 or 8.

Operating Systems

  • MacOS 10.10.0

  • Windows (32- and 64-bit) Windows 7, Windows 8, Windows 10

  • RHEL 7.0

  • Ubuntu 15.04 or later

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

Although the steps to solve these performance issues vary depending on your antivirus software, a typical solution is to either allow or exclude the Anypoint Studio and java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for McAfee Viruscan, Windows Defender, and Symantec Endpoint Protection.

Known Issues

  • Anypoint Studio freezes during start up if your installed JDK runtime is 1.8 Update 152 (1.8.0_152) or greater.
    It is recommended that you downgrade back to 1.8.0_151.

  • Communication with Exchange fails when integrating with Anypoint Platform Private Cloud Edition.

Migration Guide

Users running Studio 6.0 can update to this new version directly from the Studio Update Site.

Updating your Anypoint Studio version using the update site does not update the bundled version of the Mule runtime.
To get the latest runtime version after updating Studio follow these steps.

If you are running an older version than Studio 6.0, then instead of updating your existing version of Studio, you would need to download and run the latest installer to install a fresh new full copy.

When opening a previous workspace with projects that were created with Studio 5.1.0 or older, and which has metadata stored in disk, Studio asks you to perform an update to all the projects so that the Metadata Manager can handle the existing types and show them in your project.

You can easily import all of the external components that you had installed in your old version of Anypoint Studio through a single action. This includes connectors, runtimes, and any other type of extension added through the Anypoint Exchange or the ​Help → Install new software​ menu, as long as there are no compatibility restrictions.

Do this by selecting File→Import and then choose Install→From existing installation.


Then specify the location of your old version of Anypoint Studio in your local drive.

JIRA Ticket List for Anypoint Studio

Bug Fixes

  • STUDIO-9100 - Renaming a flow ref / batch ref on the canvas doesn’t work

  • STUDIO-9164 - Maven: cancel build does not work

  • STUDIO-9211 - Wrong metadata propagation when defining headers and using Apikit router

  • STUDIO-9285 - Support changing url to Exchange 1.0 for consuming but not for uploading artifacts

  • STUDIO-9297 - DataWeave output display corrupted characters on Windows with non ascii characters in dwl

  • STUDIO-9373 - Import from Design Center: when an error is thrown the focus is set to the Browse API window locking the UI for the user

  • STUDIO-9562 - Console V4 rendered in Studio 6.3.0

  • STUDIO-9579 - Copybook import generates schema, but can’t be set as metadata

  • STUDIO-9641 - [SE-6130] Data Mapper migrator doesn’t do anything

  • STUDIO-9657 - [Import from Design Center] Issue when retrieving api with folders.

  • STUDIO-9660 - A java.lang.NullPointerException it’s being generated during the configuration and building of a JSON output in a Transform Message on Anypoint Studio

  • STUDIO-9661 - Cannot install non-devkit connectors from Exchange (feature id format)

  • STUDIO-9668 - Cannot configure HTTP Request Configuration using RAML spec with dependencies from Exchange

  • STUDIO-9686 - Remove (beta) label from Excel Custom Metadata

  • STUDIO-9699 - [Custom Policies] Add Mule Debugger configuration when debugging a custom policy project

  • STUDIO-9700 - Studio is incorrectly validating RAML in .repository

  • STUDIO-9703 - Windows 7 Mouse scroll wheel changes outbound HTTP paramters

  • STUDIO-9720 - Munit flow reference validation error

  • STUDIO-9779 - Error when creating project with ApiKit definition

  • STUDIO-9794 - Debugging not working in Studio

  • STUDIO-9803 - MuleClassLoader is not being close generating some high memory consumption

  • STUDIO-9827 - [Publish to exchange] Add the logic from studio 7 in order to publish to exchange without a preset settings.xml

  • STUDIO-9834 - [Publish to exchange] Wrong filter for organizations does not allow publish to exchange

  • STUDIO-9874 - [FV] Can’t create a mule project in from an API spec in the VCS if I’m using STGXDR environment

  • STUDIO-9875 - When dragging and dropping a Transformer, an error is thrown.

  • STUDIO-9879 - Soap router should log error message when soap action is not defined

  • STUDIO-9934 - Step debugging show different path in graphical mode

  • STUDIO-9936 - [SE-5814] Remove flow-ref and batch-ref automatic renaming

  • STUDIO-9997 - Shared domain configuration XML file gets corrupted by Studio while configuring a connector configuration that exists in a shared domain configuration XML file

  • STUDIO-1000 - [Publish to exchange] The publish is not checking the Exchange Contributor permission to publish

Enhancement Request

  • STUDIO-9103 - Allow property placeholder for flow initial state

  • STUDIO-9552 - Validate project name to avoid special characters


Was this article helpful?

💙 Thanks for your feedback!

Submit your feedback!
Share your thoughts to help us build the best documentation experience for you!
Take our latest survey!