jedis icon indicating copy to clipboard operation
jedis copied to clipboard

Redis Java client

Results 259 jedis issues
Sort by recently updated
recently updated
newest added

### Expected behavior **Java Jedis client work with thousands of reads and write on redis server.** ### Actual behavior Jedis client gives `Could not get a resource from the pool`...

### Expected behavior `make test` should shutdown/kill all created Redis instances even if there are some errors. It does this in case of `BUILD SUCCESS`. ### Actual behavior Redis instances...

testing
stale

Hi, implementation come from #1455 with a fix on the multi close issues. Regards.

stale

Bumps [com.google.code.gson:gson](https://github.com/google/gson) from 2.10.1 to 2.11.0. Commits 828a97b [maven-release-plugin] prepare release gson-parent-2.11.0 93bc0f2 Skip signing graal-native-test module. (#2675) b153ca1 [maven-release-plugin] rollback the release of gson-parent-2.11.0 0e3d2aa [maven-release-plugin] prepare for next...

dependencies

## AFTER #3826

feature
experimental

and remove hashing of CommandObject(s).

experimental

### Expected behavior Failed to perform put and get operations into Redis Here is the stack trance ``` redis.clients.jedis.exceptions.JedisConnectionException: Failed to connect to any host resolved for DNS name. at...

### Discussed in https://github.com/redis/jedis/discussions/3874 Originally posted by **ngavrailov** June 27, 2024 ![Screenshot 2024-06-26 at 17 12 28](https://github.com/redis/jedis/assets/11725117/ec629b65-1d88-4480-8df5-4a3c7bd02bd0) Hello, What is the point of this change? Currently we are having issues...

bug

### Expected behavior connect success ### Actual behavior Write here what happens instead ... redis.clients.jedis.exceptions.JedisConnectionException: Failed to connect to any host resolved for DNS name. at redis.clients.jedis.DefaultJedisSocketFactory.connectToFirstSuccessfulHost(DefaultJedisSocketFactory.java:63) ~[jedis-5.1.2.jar:?] at redis.clients.jedis.DefaultJedisSocketFactory.createSocket(DefaultJedisSocketFactory.java:89)...

Hello! I migrated from Jedis version 3.10.0 to 5.1.3, and I noticed an increase in the execution time of GET and SET operations through the Datadog trace, as you can...