Context
PR valkey-io/valkey-glide#5793 (commit 613b0bd) was merged on 2026-05-29, bringing standalone JedisPool to near-parity with upstream Jedis pooling behavior. The documentation site's supported-features page still reflects the prior "limited support" status.
What changed in valkey-glide
JedisPool now fully supports core Jedis-style pooling: getResource(), try-with-resources / close(), Pool#returnBrokenResource, broken vs healthy return, and GenericObjectPoolConfig honored via Commons Pool 2.GlideJedisFactory#validateObject now uses PING for connection validation (supports testOnBorrow).Jedis tracks a broken flag; close() routes to returnBrokenResource when broken.Transaction (MULTI/EXEC) propagates broken state to pooled connections on failure.- Migration guide in the source repo was updated accordingly.
Required documentation changes
File: src/content/docs/migration/java/jedis/jedis-compatibility-layer/supported-features.mdx
Client Types section
- Change
⚠️ JedisPool (limited support) → ✅ JedisPool (standalone) with a note: "Core Jedis-style pooling — getResource(), try-with-resources / close(), Pool#returnBrokenResource, broken vs healthy return, GenericObjectPoolConfig honored via Commons Pool 2. Each pooled Jedis uses its own GLIDE GlideClient."
JedisPooled remains ⚠️ (unchanged).
Connection Management section
- Remove or update: "JedisPool advanced configurations: Complex pool settings not fully supported" —
GenericObjectPoolConfig is now honored.
- Remove: "Connection pooling: Native Jedis pooling mechanisms not implemented" — standalone pooling is implemented.
- Add: "JedisSentinelPool / Sentinel: Not provided by this compatibility layer."
- Add architecture note: standalone
JedisPool maps each pool slot to one GlideClient.
Configuration Limitations section
- Update "Connection validation: Jedis connection health checks unavailable" → "Connection validation: When Commons Pool validation is enabled (e.g.
testOnBorrow), GlideJedisFactory#validateObject uses PING; tune pool config as needed."
Advanced Features section
- Consider updating "Transactions: MULTI/EXEC transaction blocks not supported" since
Transaction class with multi()/exec() is now functional.
Reference
Context
PR valkey-io/valkey-glide#5793 (commit
613b0bd) was merged on 2026-05-29, bringing standaloneJedisPoolto near-parity with upstream Jedis pooling behavior. The documentation site's supported-features page still reflects the prior "limited support" status.What changed in valkey-glide
JedisPoolnow fully supports core Jedis-style pooling:getResource(), try-with-resources /close(),Pool#returnBrokenResource, broken vs healthy return, andGenericObjectPoolConfighonored via Commons Pool 2.GlideJedisFactory#validateObjectnow uses PING for connection validation (supportstestOnBorrow).Jedistracks abrokenflag;close()routes toreturnBrokenResourcewhen broken.Transaction(MULTI/EXEC) propagates broken state to pooled connections on failure.Required documentation changes
File:
src/content/docs/migration/java/jedis/jedis-compatibility-layer/supported-features.mdxClient Types section
⚠️ JedisPool (limited support)→✅ JedisPool (standalone)with a note: "Core Jedis-style pooling —getResource(), try-with-resources /close(),Pool#returnBrokenResource, broken vs healthy return,GenericObjectPoolConfighonored via Commons Pool 2. Each pooledJedisuses its own GLIDEGlideClient."JedisPooledremains⚠️(unchanged).Connection Management section
GenericObjectPoolConfigis now honored.JedisPoolmaps each pool slot to oneGlideClient.Configuration Limitations section
testOnBorrow),GlideJedisFactory#validateObjectuses PING; tune pool config as needed."Advanced Features section
Transactionclass withmulti()/exec()is now functional.Reference