Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 6.6 with Mule Runtime Engine 3.9.3 Update Site 2 Release Notes

Anypoint Studio 6.6 with Mule Runtime Engine 3.9.3 Update Site 2 Release Notes

September 20, 2019+ Build ID: 201909191757

Skip to Migration Guide

Compatibility

Mule runtime engine

Version: 3.9.3 EE

Anypoint Studio

Version: 6.6.2
Build Id: 201909191757

APIkit

Versions: 3.9.3

DataWeave

Version: 1.2.3

MUnit

Version: 1.7.4 (munit-studio-plugin)

SAP Connector

Versions: 3.2.1

Eclipse

Versions: 4.7.2

What’s New

The Anypoint Studio 6.6.2 release includes a number of bug fixes and comes with Mule runtime engine version 3.9.3.

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

This version of Anypoint Studio requires AdoptOpenJDK 8 to run properly.

Depending on which Mule runtime engine you want to use, you can configure different JDK versions within Anypoint Studio:

  • 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 sometimes removes new changes made to a mavenized project.

Migration Guide

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

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.

import

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

JIRA Ticket List for Anypoint Studio

Bug Fixes

  • Fixed issue where Mimetype autocomplete did not work in every possible XML tag.

  • Fixed slow parsing of RAML resource.

  • Fixed issue where Studio did not refresh some files in your Workspace that were modified outside of Studio, even when using the Refresh functionality in the Package Explorer view.

  • Fixed issue where a Git merge conflict was caused by order of entries changed in mule-deploy.properties file.

  • Fixed issue where metadata was not being displayed in flow variable section when using Advanced Target on Database Connector.

  • Fixed issue where the Load more apis button was absent and not all APIs were showing when connecting to API Manager.

  • Fixed issue where Connect project to API Manager feature did not show all APIs available.

  • Fixed issue where a user was unable to set anypoint.platform.gatekeeper to anything other than false in Studio.

  • Fixed issue where an error was thrown when trying to edit router configuration and using nested includes.

  • Fixed issue where IPV6 was not supported in the HTTP Listener.

  • Fixed issue where closing projects in Studio was very slow.

  • Fixed issue where Studio was not properly resolving includes in windows.

  • Fixed issue where a dependency was not being added to the POM file when generating flows from WSDL.

  • Fixed issue where exceptions were thrown when opening logs and refreshing projects.

  • Fixed issue where create project from apikit failed when using includes in Windows.

  • Fixed issue where parsing RAML in Studio on Windows resulted in errors.

  • Fixed issue where RAML 0.8 files threw errors when parsing due to a wrong snakeyaml.

  • Fixed issues resolving WSDL location.

  • Fixed issue where Create Apikit Project From URL option using raml10 failed.

  • Fixed issue where dragging and dropping a with filter in Dataweave incorrectly concatenated an extra map.

  • Fixed issue where Studio duplicated metadata:id attributes when dragging and dropping a Transform Message component from a flow to a subflow.

  • Fixed thread deadlock issue when running Studio 6.6.1 on Windows.

Tasks

  • Upgraded the embedded runtime to Mule runtime engine 3.9.3.

  • Reviewed metrics to avoid sending sensitive data to Amplitude.

  • Stabilized the rcptt Studio 6 sanity suite.

Enhancement Request

No enhancement requests were addressed in this release.

Support