---
schema_version: "1"
id: 04dea6fd2bac9d83f092d888c69b2e346b7b30c14ea770595eb025235adccb8c
title: Redis Connector Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/connector/redis-connector-release-notes-mule-4.md
canonical_url: https://docs.mulesoft.com/release-notes/connector/redis-connector-release-notes-mule-4
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 154746026ea0d9b67fa760cb0c41724c2546a5277d98b4de4647e018277ce056
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Redis Connector Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Support Category:
[Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)

Anypoint Connector for Redis (Redis Connector) provides access to an open-source advanced key-value
store that is often referred to as a data structure server because the keys can contain strings,
hashes, lists, sets, and sorted sets.

The Redis Connector offers complete support for its CRUD API.

Guide: [Redis Connector](https://docs.mulesoft.com/redis-connector/latest/)  
Reference: [Redis Connector Reference](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference)

## 5.8.1

**September 21, 2026**

### What’s New

- This release includes general security fixes.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 5.8.0

**August 21, 2026**

### What’s New

- The connector now includes the optional **Socket Timeout** and **Socket Time Unit** fields on the
  **Clustered**, **NonClustered**, and **Sentinel** connection types. Use these fields on the
  connection **Advanced** tab to set an independent read timeout for Redis command responses. Leave
  **Socket Timeout** empty to reuse **Connection Timeout** as the read timeout, which preserves the
  previous single-timeout behavior.

  For more information, see
  [Clustered](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_clustered),
  [NonClustered](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_nonclustered), and
  [Sentinel](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_sentinel).

- The Jedis client is upgraded to 7.5.3.

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <a href="https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#redis_clustered">Clustered</a> connection now applies pooling settings such as <strong>Max Total</strong> and <strong>Max Wait Millis</strong> to the cluster client, instead of ignoring those values.</p></div></div></td><td><div><div><p>W-23857760</p></div></div></td></tr><tr><td><div><div><p><code>REDIS:UNKNOWN</code> errors no longer occur when the <a href="https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#set">Set</a> operation runs with <strong>If Not Exists</strong> set to <code>true</code> on a key that already exists. The operation now returns null and leaves the existing value and TTL unchanged.</p></div></div></td><td><div><div><p>W-23546930</p></div></div></td></tr></tbody></table>

## 5.7.0

**June 25, 2026**

### What’s New

- The Jedis client is upgraded to 7.5.2.

- The connector now includes the new **Username** field for all connection types to enable ACL
  authentication. For the **Sentinel** connection type, you can also configure the **Sentinel
  Username** field to set independent credentials for the sentinel nodes. Use these fields alongside
  the existing password fields to authenticate to Redis servers that require ACL credentials. ACL
  authentication requires Redis server 6.0 or later. Connections that omit a username continue to
  use password-only authentication.

  For more information, see
  [Redis Connector Reference](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference).

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 5.6.0

**May 4, 2026**

### What’s New

- The connector now includes the new **TLS Configuration** and **Endpoint identification algorithm**
  fields for the **Sentinel** connection type. Use these fields to configure the communication
  protocol and select the algorithm used by clients to validate the server host name via TLS/SSL.

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 5.5.0

**February 19, 2026**

### What’s New

- The connector is now compatible with Redis 8.x (Jedis 7.2.1).

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, 7.2.x, and 8.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The connector now correctly handles the <strong>Connection Time Unit</strong> value for the <strong>Clustered</strong> connection type so that the timeout is properly converted based on the specified time unit. Previously, the <strong>Connection Time Unit</strong> value was treated as milliseconds regardless of the configured unit, causing immediate connection failures.</p></div></div></td><td><div><div><p>W-21246508</p></div></div></td></tr></tbody></table>

## 5.4.7

**May 2, 2025**

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>4.4.8</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, and 7.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Thread leaks no longer occur if invoked with the <strong>Set</strong>, <strong>Get</strong>, or <strong>Del</strong> operations using dynamic configuration.</p></div></div></td><td><div><div><p>W-17880825</p></div></div></td></tr></tbody></table>

## 5.4.6

**August 22, 2024**

### What’s New

- This connector is now compatible with Redis server 7.

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>4.4.8</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, 6.2.x, and 7.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 5.4.5

**June 6, 2024**

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>3.10.0</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <strong>Entry TTL</strong> field for RedisObjectStore is now transformed correctly from Long to Integer and from milliseconds to seconds. Additionally, Mule apps that use an Object Store entry TTL exceeding 24 days now observe that the TTL for new keys is set to the correct values.</p></div></div></td><td><div><div><p>W-14745160</p></div></div></td></tr></tbody></table>

## 5.4.4

**March 8, 2024**

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>3.10.0</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The RedisObjectStore remove operation now correctly returns the stored value associated with the removed key, aligning with the Object Store interface specification. Previously, the connector erroneously returned a Long value representing the outcome of the underlying <strong>Del</strong> operation. This change can affect backward compatibility for custom Mule apps that rely on the previous behavior. However, it does not impact the Redis Connector or RedisObjectStore in Mule apps, as these usages are implemented correctly. The change affects direct usage of RedisObjectStore within custom applications.</p></div></div></td><td><div><div><p>W-14809749</p></div></div></td></tr></tbody></table>

## 5.4.3

**February 2, 2024**

### What’s New

- This connector is now compatible with Java 17.

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>3.10.0</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 5.4.2

**June 14, 2023**

## Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>3.10.0</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8 and 11</p></td></tr></tbody></table>

### What’s New

- Upgraded the Jedis client to version 3.10.0.

## 5.4.1

**February 18, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis Java Client</p></td><td><p>3.5.1</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x, 6.0.x, and 6.2.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8 and 11</p></td></tr></tbody></table>

### Features

Upgraded the Jedis client to version 3.5.1.

## 5.4.0

**January 20, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8 and 11</p></td></tr></tbody></table>

### Features

- Added the Trim From List and Range From List operations.

## 5.3.0

**September 14, 2020**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8 and 11</p></td></tr></tbody></table>

### Features

- Added a sentinel connection provider that enables you to connect to a Redis instance that is
  configured to run in sentinel mode.

## 5.2.0

**August 3, 2020**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, 5.0.x and 6.0.x</p></td></tr></tbody></table>

### Features

- Added support for TLS.

- Upgraded the jedis client version to 3.3.0.

## 5.1.3

**June 29, 2020**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x</p></td></tr></tbody></table>

### Fixed Issues

- When using the Set operation with TTL, the operation correctly set the specified value, but did
  not set the expire time. The connector now uses the Redis SET operation to set the expire time.
  (SE-16101)

## 5.1.2

**November 25, 2019**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x</p></td></tr></tbody></table>

### Fixed Issues

- Fixed order issue for both ascending and descending orders in the
  [Get Range By Score](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#getRangeByScore) and
  [Get Range By Index](https://docs.mulesoft.com/redis-connector/latest/redis-connector-reference#getRangeByIndex)
  operations. (SE-13883)

## 5.1.1

**June 6, 2019**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.0 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, 3.2.x, 4.x, and 5.0.x</p></td></tr></tbody></table>

### Fixed Issues

- Redis connector 5.1.0 test connection always return successful. This issue was fixed by making
  sure the Redis instance being used is actually up and running by sending an ECHO command to it.
  (SE-11775)

## 5.1.0

**April 22, 2019**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.0 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, and 3.2.x</p></td></tr></tbody></table>

### Features

Added support so that the Redis connector can be used as a custom object store in a Mule
application.

## 5.0.0

**November 18, 2017**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.0 and later</p></td></tr><tr><td><p>Redis server</p></td><td><p>2.8.x, 3.0.x, and 3.2.x</p></td></tr></tbody></table>

### Features

Migrated to Mule 4.0.0 and later runtime.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [MuleSoft Services](https://www.mulesoft.com/support-and-services)

- [Known Issues](https://help.salesforce.com/s/issues)