Nav

Anypoint MQ Cloud Release Notes

November 5, 2016

Anypoint MQ provides MuleSoft’s cloud and enterprise messaging service. 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.

See Also:

Version 1.5.0 - January 14, 2017

This release of Anypoint MQ introduces the following new features:

  • FIFO queues

  • Exactly once delivery

  • Rollout of Anypoint MQ to US-West (Oregon) region

  • Enables encoding and support for UTF-8/non-ascii characters.

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

MQ-572

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.

MQ-556

Fixed memory leak that occurred when reporting usage metrics

MQ-548

Created support for sending a message without a body

MQ-543

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

MQ-535

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

MQ-534

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 that enables a queue to receive undeliverable messages. For more information, see Dead Letter Queues.

  • Bug fixes and UI improvements.

The Anypoint MQ API allows you to 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

MQ-339

Ability to use Dead Letter Queues

MQ-488

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

MQ-489

Add a new header to messages specifying the encoding

MQ-493

Dead Letter Queue UI

MQ-507

Return the error status when creating a queue with no body

MQ-511

Usage of correct property attributes for retry policy

MQ-531

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

MQ-391

UI for usage tracking

MQ-394

Metrics Query API

MQ-404

MQ detailed usage pane and improvements to other UI screens

MQ-411

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

MQ-412

Cannot get statistics of queues

MQ-413

Broker API - Cannot get message

MQ-416

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

MQ-420

Better error messages and logging for stats/analytics requests

MQ-434

Support histograms of message sizes per queue

MQ-442

Support MQ billing management

MQ-444

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

MQ-445

Some components doesn’t look properly

MQ-446

Several errors in modal to create a queue

MQ-449

When deletes a queue it displays "Deletion Fail" message even when doesn’t fail

Version 1.1.2 - May 14, 2016

This release provides user interface updates and bug fixes.

Fixed Issues

Issue Description

MQ-327

Message browser list should not be ordered by message ID

MQ-357

Add IDs to HTML elements for test automation

MQ-374

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

MQ-385

Integrate notifications with analytics for billing

MQ-388

[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.

Features

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

MQ-201

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

MQ-205

Enforced maximum message size limit to 10 MB

MQ-241

Exchange historical statistics as delta from 0

MQ-301

Ability to count delivered/received messages

MQ-306

Request to non-existing API returns bad error message

Version 1.0.1 - January 23, 2016

Features:

  • Anypoint MQ now supports use with Internet Explorer 11.

Version 1.0.0 - December 21, 2015

This release includes the following capabilities:

  • Queues and 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

  • If you need to specify UTF-8 characters greater than U+007F in a message that you send to an Anypoint MQ queue or exchange, first uuencode the message before sending, and use uudecode after retrieving the message. The use of uuencode makes the message into an ASCII text string.

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