-
Notifications
You must be signed in to change notification settings - Fork 3k
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
minimumIdle=0 means no limit? #115
Labels
Comments
It is a bug. |
I will appreciate it if you can fix it soon:) |
brettwooldridge
added a commit
that referenced
this issue
Jul 22, 2014
This is fixed in the |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just want to obtain
HikariDataSource
with no connections initially as backup datasources, but I found that it still reachmaximumPoolSize
after a while when I never invokegetConnection()
on this dataSource.Then I found this piece of code:
It seems the house keeper thread create one connection each time when minIdle==0, until reach maxPoolSize...
I am wondering why doing things like that? Can we just do nothing when minIdle==0?
The text was updated successfully, but these errors were encountered: