You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
some redis session key can be never expires ,with ttl=-1
To Reproduce
Steps to reproduce the behavior.
spring cloud gateway 4.0.7+spring-session-data-redis 3.1.3+redisson-spring-boot-starter 3.23.5
Expected behavior
any redis session key should hava a exipiration;
Sample
send any request to the gateway to create session,
open the redis-cli monitor:
1697092184.031780 [0 10.18.137.27:49859] "EXPIRE" "gateway.spring.session:sessions:fb7eb55a-4999-4e3f-af73-479efe70f343" "3600"
1697092184.031939 [0 10.18.137.27:49861] "HMSET" "gateway.spring.session:sessions:fb7eb55a-4999-4e3f-af73-479efe70f343" "sessionAttr:
as if the commands execution order is random,
if expire command xecutes before the hmset,the expiration time will not work;
if expire command xecutes after the hmset,the expiration time work as expected;
so the keys' ttl will be the default value:-1
The text was updated successfully, but these errors were encountered:
Describe the bug
some redis session key can be never expires ,with ttl=-1
To Reproduce
Steps to reproduce the behavior.
spring cloud gateway 4.0.7+spring-session-data-redis 3.1.3+redisson-spring-boot-starter 3.23.5
Expected behavior
any redis session key should hava a exipiration;
Sample
send any request to the gateway to create session,
open the redis-cli monitor:
1697092184.031780 [0 10.18.137.27:49859] "EXPIRE" "gateway.spring.session:sessions:fb7eb55a-4999-4e3f-af73-479efe70f343" "3600"
1697092184.031939 [0 10.18.137.27:49861] "HMSET" "gateway.spring.session:sessions:fb7eb55a-4999-4e3f-af73-479efe70f343" "sessionAttr:
as if the commands execution order is random,
if expire command xecutes before the hmset,the expiration time will not work;
if expire command xecutes after the hmset,the expiration time work as expected;
so the keys' ttl will be the default value:-1
The text was updated successfully, but these errors were encountered: