The com.fasterxml.jackson.core library is upgraded to version 2.13.3 to address reported security vulnerabilities.
Amazon SQS Connector Release Notes - Mule 3
Support Category: Select
Anypoint Connector for Amazon SQS (Amazon SQS Connector) provides an easy way to interface with the Amazon SQS API, allowing users to manage SQS queueing services without having to directly work with the API.
Starting with v.4.0.0, Amazon SQS Connector is licensed commercially with Anypoint Platform as with other Select connectors. Prior versions remain freely available to the community.
Guide: Amazon SQS Connector
Reference: Amazon SQS Connector Reference
4.4.8
August 8, 2022
What’s New
-
The com.fasterxml.jackson.core library is upgraded to version 2.13.3 to address reported security vulnerabilities.
Compatibility
Application/Service | Version |
---|---|
Mule |
3.6.0 and later |
AWS SDK for Java |
1.11.611 |
Connector DevKit |
3.9.8 |
Fixed Issues
Issue | ID |
---|---|
W-11555340 |
4.4.2
4.3.1
November 27, 2018
Fixed Issues
-
The connector was intermittently failing to parse the HTTP response and was throwing an exception. This was fixed by updating the AWS library used.
-
There was a thread leak caused by the fact that the AWS client used by the connector was recreated each time a request was submitted to the SQS API.
4.3.0
November 2, 2018
Features
-
The Amazon SQS Connector now supports Canada (Central) (ca-central-1) and EU (London) (eu-west-2)
Fixed Issues
-
Connector continued retrieving messages when a flow was stopped - In previous versions the connector continued retrieving messages after the Mule app was stopped. In the current version, after the Mule app stops, the connector stops retrieving messages.
-
Multiple connections established - Previously, the connector would make a high number of connections, even if the polling was set to a high value.
-
Connector stopped working after receiving a 500 error from Amazon - The connector stopped receiving messages when a Status Code 500 was received from Amazon. This was fixed, and the connector attempts a reconnection in cases like this.
4.2.1
December 19, 2017
Compatibility
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
AWS SDK for Java |
1.11.79 |
Connector DevKit |
3.9.4 |
Fixed Issues
-
messageId
andmd5OfMessageAttributes
swapped - In previous versions the messageId was mapped to the md5OfMessageAttributes attribute and vice versa. In version 4.2.1, these attributes are correctly mapped. -
SendMessageBatchREquestEntry
SQS DataType only from Java code - In past versions, the only way to useSendMessageBatchREquestEntry
SQS DataType was by using Java Code. In version 4.2.1, it is also possible by DataWeave. -
Test Connection fails when queue name contains dot (".") character - In past versions when the name contained a dot character, Test Connection failed when using the queue name. In version 4.2.1, the TestConnection works correctly.
-
App hangs after stopping and restarting sequence - In the previous version when stopping the application and then restarting it, the application hung with an
org.mule.api.lifecycle.LifecycleException
. In version 4.2.1, the stop and restart sequence works correctly.
4.2.0
March 30, 2017
Features
-
FIFO queue support in addition to standard queues. FIFO queues ensure the order of messages.
-
AssumeRole for authentication in addition to IAM AccessKey and SecretKey.
Fixed Issues
-
In earlier versions, when the Amazon SQS Connector is used as an inbound endpoint, the custom exception strategy could not be invoked, and the source stopped polling for messages when an exception occurred. Now SQS as a source does not stop polling messages when an uncaught exception and custom exception strategy can be invoked.
-
Handling of binary attributes in sendMessage operation.
4.1.0
September 30, 2016
Compatibility
Application/Service | Version |
---|---|
Mule |
3.6.0 and later |
AWS SDK for Java |
1.11.21 |
Connector DevKit |
3.9.0 |
Features
-
Amazon SQS Connector is built with Connector DevKit v3.9.0
-
Upgraded to AWS SDK to v1.11.21
-
Support for Temporary Credentials - A checkbox named Try Default AWS Credentials Provider Chain has been added to the Global Element configuration. If selected, the connector will first try to obtain the credentials from a AWS environment.
-
Support for Retry Policy - The connector will perform a maximum of 10 retries when a request fails due to server-side throttling or dropped connection.
3.1.1
-
Upgraded to Connector DevKit v3.7.0
-
The Test Connection feature in the Global Configuration settings has been modified to test queue level action rather than the generic system wide Amazon SQS action.
-
The prefix
Proxy
for all the parameters in Proxy Settings has been removed. -
Fixed exception handling of shaded exceptions thrown by the connector.
-
Data type for Message Attributes retrieved by Receive Messages Source has been fixed.
3.0.0
June 9, 2015
Compatibility
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
AWS SDK for Java |
1.9.39 |
Connector DevKit |
3.6.1 |
Features
-
Upgraded AWS SDK for Java to 1.9.39
-
Upgraded Connector DevKit to 3.6.1
-
Added the following new operations:
-
ChangeMessageVisibility
-
ChangeMessageVisibilityBatch
-
CreateQueue
-
DeleteMessageBatch
-
ListDeadLetterSourceQueues
-
ListQueues
-
PurgeQueue
-
SendMessageBatch
-
-
Renamed the GetURL operation to Get Queue URL
-
Added support for proxy settings
2.5.1
-
Added support for sending message attributes.
-
Updated AWS JAVA SDK version to 1.7.13.
-
Improved the performance of the
receiveMessages
operation using asynchronous delivery instead of polling. ThepollPeriod
parameter has been preserved but deprecated to maintain backwards compatibility. -
Bug fix: Message source threads weren’t shutting down when Mule shut down or was redeployed, causing applications to hang. This has been fixed now.
2.3.1
-
Upgraded Connector DevKit to v3.5.0.
-
Added Studio interoperability tests.
-
Added a 65 second sleep between tests to cater for new SQS restriction on creating and deleting a queue of the same name within 60 seconds of itself.