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
Redis sessions with no expiration time are created even if the ReactiveRedisSessionRepository.setDefaultMaxInactiveInterval(Duration) is set. This happens when the app is high loaded
To Reproduce
Let's load the app using JMeter with 75 threads/users. Each request invokes the endpoint that creates a new session using session.changeSessionId(). About 10 minutes later we should notice that among sessions with ttl set, there is a few sessions with no ttl appear
Expected behavior
If ReactiveRedisSessionRepository.setDefaultMaxInactiveInterval(Duration) then all created sessions should have ttl set, even on high loads
The text was updated successfully, but these errors were encountered:
Describe the bug
Redis sessions with no expiration time are created even if the
ReactiveRedisSessionRepository.setDefaultMaxInactiveInterval(Duration)
is set. This happens when the app is high loadedTo Reproduce
Let's load the app using JMeter with 75 threads/users. Each request invokes the endpoint that creates a new session using
session.changeSessionId()
. About 10 minutes later we should notice that among sessions with ttl set, there is a few sessions with no ttl appearExpected behavior
If
ReactiveRedisSessionRepository.setDefaultMaxInactiveInterval(Duration)
then all created sessions should have ttl set, even on high loadsThe text was updated successfully, but these errors were encountered: