Last checked and updated on 10 Jun 2026
What Is New in Jedis 2.5
Jedis 2.5 delivers a solid set of updates focused on new Redis commands, internal improvements, and essential bug fixes. This release keeps the client aligned with the latest Redis server capabilities while enhancing stability.
| Category | Key Changes |
|---|---|
| New Features | Support for ACL commands, JSON commands, and other new Redis operations. |
| Improvements | Connection pool and internal exception handling refinements. |
| Bug Fixes | Resolved issues with connection validation and command execution. |
| Deprecated | Methods related to the old 'maxActive' pool configuration. |
What new Redis commands were added?
Jedis 2.5 adds support for several important Redis command groups. This brings the client up to speed with newer server features that developers are starting to rely on.
ACL Commands
Full support for Redis Access Control List commands is now included. You can programmatically manage users and permissions with methods like aclSetUser(), aclGetUser(), and aclDelUser().
JSON Commands
For projects using the RedisJSON module, Jedis now provides native support. This lets you work directly with JSON data types stored in Redis without manual serialization.
Other Additions
The release also includes other miscellaneous commands such as LMOVE, BLMOVE, ZDIFF, ZINTER, and ZUNION, expanding the toolkit for data structure operations.
How did connection handling get better?
The core connection and pool mechanics saw meaningful refinements. These changes are about making the client more robust and easier to debug in production environments.
A new JedisPoolConfig was introduced to properly support the maxTotal configuration parameter, replacing the old and confusing maxActive name. The deprecated setMaxActive() method should no longer be used.
Exception handling was also improved. The JedisDataException now includes the full error response from the Redis server, which is a huge help when troubleshooting failed commands.
What bugs were squashed in this release?
This version addresses a handful of specific bugs that could cause headaches. The fixes are targeted and improve overall reliability.
One key fix resolves an issue where the ping() method could incorrectly throw an exception, which was problematic for connection health checks. Another fix ensures the BITPOS command handles its parameters correctly.
The validation logic when returning connections to the pool was also corrected, preventing a potential resource leak scenario.
FAQ
Is the old 'maxActive' pool parameter completely gone?
Yes, the old terminology is deprecated. You should migrate your pool configuration to use setMaxTotal(int maxTotal) on the JedisPoolConfig object instead.
Do I need the RedisJSON module to use the new JSON commands?
Absolutely. The new jsonGet(), jsonSet(), and other JSON methods require the Redis server to have the RedisJSON module installed and loaded, otherwise they will fail.
What's the main benefit of the improved JedisDataException?
It now includes the full error string from Redis. Before, you might just get a generic exception; now you get the specific error message returned by the server, which makes debugging much faster.
Was the behavior of the BITPOS command changed?
No, the command itself is the same. The bug was in the Jedis client's method signature which didn't properly handle the optional [START] and [END] parameters. This has been fixed to match the Redis specification.
Are there any breaking changes I should worry about?
Not really. The deprecation of maxActive is the main change, but it's a straightforward rename. The new features are additive, so existing code should continue to work without modification.