-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with Spring Data Redis with spring boot 3.3 #811
Comments
Can you perform the following steps?
|
01::48::45 dbug: GarnetServer[0] Accepted TCP connection from 127.0.0.1:51061 |
@badrishc and if you need, you can see Spring Data's Log Just Look to me, Garnet's Log is clear to resolve doubt to garnet. |
Very works well with when client mode in RESP v2 01::59::34 dbug: GarnetServer[0] Accepted TCP connection from 127.0.0.1:59418 |
I found that Lattuce (Java Client for Redis) has problem. |
I don't see any issues on server side Garnet logs for both resp2 and resp3. Lmk if you see anything amiss |
Yes, You right. Just Issue on Spring Data RedisI will find anwer from Spring and Thank you for your kindness Answer and support @badrishc |
The issue is created by the |
Then Fix Hello's Type after new err occur on... Umm I will find some more what is problem 05::48::43 trce: Session[0] [127.0.0.1:63882] [023C0C5D] RECV: [*4|$6|CLIENT|$7|SETINFO|$8|lib-name|$7|Lettuce|*4|$6|CLIENT|$7|SETINFO|$7|lib-ver|$21|6.3.2.RELEASE/8941aea|] |
Lettuce 6.4 (or 6.5.) switches to fire-and-forget mode for these commands (IIRC). |
Describe the bug
When I use Garnet to replace Redis
My app written in Java with Spring Boot 3.3 and Spring Data Redis
I tried to test on container side and
Redis CLI works well in PING command
also Application's Execution of Ping works well
but Spring Application Try to connect Garnet, Fail to connect
and I checked logs, and finally found, when using Hello, fault on
Steps to reproduce the bug
Expected behavior
working well
Screenshots
no prepared
Release version
v1.0.36
IDE
No response
OS version
Ubuntu 24.04 LTS Host
running on docker compose (garnet latest, eclipse-temurin:21-jre
Additional context
we operate garnet with out username and password, cause in docker network will ensure prevent to connect from external's
failed codes
successed code
The text was updated successfully, but these errors were encountered: