Anypoint MQ Cloud Release Notes

September 2017

Anypoint MQ provides cloud and enterprise messaging services in MuleSoft. Anypoint MQ lets you perform advanced asynchronous messaging scenarios between your applications and is fully integrated with Anypoint Platform, offering role-based access control, client application management, and connectors.

Locations where MQ is available: Northern Virginia (us-east-1), Ireland (eu-west-1), Singapore (ap-southeast-1), Sydney (ap-southeast-2), and Oregon (us-west-2).

See Also:

Version 1.7.4 - September 23, 2017

This release adds new functionality to the Anypoint MQ Statistics API and fixes a FIFO DLQ issue.

MQ-748 - The Statistics API provides these new metrics that apply to both FIFO and non-FIFO queues:

  • messagesVisible - The number of messages that can be retrieved from a queue.

  • messagesSent - The number of messages added to a queue.

  • messagesReceived - The number of messages received in a queue.

  • messagesAcked - The number of messages ACKed or deleted in the UI.

MQ-706 - Can now send messages to FIFO DLQs correctly.

Version 1.7.1 - July 15, 2017

FIFO access is now available in Oregon (us-west-2), Northern Virginia (us-east-1), and Ireland (eu-west-1).

Version 1.6.1 - May 20, 2017

Added MQ access to Singapore (ap-southeast-1).

Version 1.6.0 - March 25, 2017

This release of Anypoint MQ introduces the following new feature:

Version 1.5.0 - January 28, 2017

This release of Anypoint MQ introduces the following new features:

Version 1.4.0 - November 5, 2016

This release of Anypoint MQ fixes issues with Analytics usage and with OAuth.

Fixed in This Release:

Issue Description


Modify startDate and endDate in metrics to use a standard date format, such as 2016-11-01T19:00Z. This change preserves both the old format and the new format for backward compatibility.


Fixed memory leak that occurred when reporting usage metrics


Created support for sending a message without a body


When sending an Ack without bearer token, report 401 error instead of 500


Report 500 error when trying to create a queue with the same name as the dead letter queue


Return a 400 error if user tries to configure the DLQ of a queue as itself

Version 1.3.0 - August 27, 2016

This release of Anypoint MQ contains the following features:

  • Dead Letter Queue (DLQ) feature enables a queue to receive undeliverable messages.

  • Bug fixes and UI improvements.

The Anypoint MQ API lets you configure a queue to be its own dead letter queue; however, the MQ user interface does not let a queue to be its own DLQ, only the REST API permits this. MuleSoft recommends that you do not do this except for testing purposes because if left in production, this can result in infinite retries thus causing a client application to burn through its monthly usage quota quickly.

Fixed in This Release:

Issue Description


Ability to use Dead Letter Queues


Correction to encoding logic when sending messages between 200-300KB


Add a new header to messages specifying the encoding


Dead Letter Queue UI


Return the error status when creating a queue with no body


Usage of correct property attributes for retry policy


Dead Letter Queue UI state updates

Version 1.2.0 - June 25, 2016

This release of Anypoint MQ contains the following features:

Fixed in This Release:

Issue Description


UI for usage tracking


Metrics Query API


MQ detailed usage pane and improvements to other UI screens


Stats API - Standardize the date format we use for the different calls


Cannot get statistics of queues


Broker API - Cannot get message


Admin API - Operations are not being counted in analytics in the apiRequestCount field


Better error messages and logging for stats/analytics requests


Support histograms of message sizes per queue


Support MQ billing management


MQ UI should not be displayed if the organization doesn’t have it enabled


Some components doesn’t look properly


Several errors in modal to create a queue


When deleting a queue, displays "Deletion Fail" message even when there’s no failure

Version 1.1.2 - May 14, 2016

This release provides user interface updates and bug fixes.

Fixed Issues

Issue Description


Message browser list should not be ordered by message ID


Add IDs to HTML elements for test automation


[UI] Exchange Settings are not visible as soon as the user access to the details


Integrate notifications with analytics for billing


[UI][Chrome] unreadable list of queues during the creation of an exchange

Version 1.1.0 - May 5, 2016

This release is the General Availability release for Anypoint MQ.


This release includes these features:

  • Users can view and track their MQ usage.

  • 10 MB maximum message size limitation is now enforced.

  • Updated API error and return codes reflect the proper status.

Fixed in This Release

Issue Description


(Admin API) The system returns 204 ok even when the org ID doesn’t exist


Enforced maximum message size limit to 10 MB


Exchange historical statistics as delta from 0


Ability to count delivered/received messages


Request to non-existing API returns bad error message

Version 1.0.1 - January 23, 2016


  • Anypoint MQ now supports use with Internet Explorer 11.

Version 1.0.0 - December 21, 2015

This release includes the following capabilities:

  • Queues and Message Exchanges: Send messages to queues, pull messages from queues, create a message exchange to perform pub/sub scenarios and send a message to multiple queues. Management console: monitor queue statistics, purge queues, and see how many messages are in flight via the management console.

  • Anypoint MQ connector: Send/receive messages from any Mule application, whether it’s deployed in CloudHub or used in a hybrid scenario and deployed on-premises.

  • Client management: Create client applications tokens.

  • Large payloads: Anypoint MQ supports payloads up to 10 MB in size.

  • Disaster recovery and multi-data center availability: Anypoint MQ provides persistent data storage across multiple data centers, ensuring that it can handle data center outages and have full disaster recovery.

  • Encrypted queues: Queue data can optionally be encrypted, ensuring that companies can be compliant with their data at rest policies.

Known Issues

  • None

For known issues affecting only the Anypoint MQ connector, see Anypoint MQ Connector Release Notes.

See Also