-
Notifications
You must be signed in to change notification settings - Fork 55
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
Default maxLifeTime value result in immediate eviction of all connections #129
Labels
Milestone
Comments
Care to submit a pull request to fix the problem? |
Sure, will do! |
patriknw
added a commit
to patriknw/r2dbc-pool
that referenced
this issue
Feb 5, 2022
patriknw
added a commit
to patriknw/r2dbc-pool
that referenced
this issue
Feb 5, 2022
Signed-off-by: Patrik Nordwall <[email protected]>
patriknw
added a commit
to patriknw/r2dbc-pool
that referenced
this issue
Feb 5, 2022
Signed-off-by: Patrik Nordwall <[email protected]>
Just a friendly ping, could someone merge this PR? |
Current workaround: set |
mp911de
pushed a commit
that referenced
this issue
Jun 22, 2022
[resolves #129][#155] Signed-off-by: Patrik Nordwall <[email protected]>
mp911de
pushed a commit
that referenced
this issue
Jun 22, 2022
[resolves #129][#155] Signed-off-by: Patrik Nordwall <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug Report
The default for maxLifeTime is defined as
NO_TIMEOUT = Duration.ofNanos(-1)
, which is supposed to mean "No timeout". However, the current implementation of actual evectionPredicate, attempts to dotoMillis
conversion, which results in0
, thus resulting in theif (maxIdleTimeMills == 0 || maxLifeTimeMillis == 0)
always returningtrue
.Possible Solution
Replace
maxLifeTimeMillis == 0
withmaxLifeTime.isZero()
.The text was updated successfully, but these errors were encountered: