10762d6403
Tighten-up addBagItem() implementation with cleaner loop.
10 years ago
8aa2034709
Fixes #222 separate responsibility of maintaining idle connections from addBagItem(). addBagItem() will now add exactly one connection per-invocation (with retry). Create a separate fillPool() method to handle idle connection maintenance.
10 years ago
8a61e581c2
Fix ConcurrentBag test
10 years ago
467bc2f79a
Simple variable rename for clarity
10 years ago
c3043d8f9d
Re-use the assassin executor.
10 years ago
ed2fa1b513
[maven-release-plugin] prepare for next development iteration
10 years ago
873ab10a1c
[maven-release-plugin] prepare release HikariCP-2.3.0-rc3
10 years ago
373c29017a
[maven-release-plugin] rollback the release of HikariCP-2.3.0-rc3
10 years ago
e9134aaa8b
[maven-release-plugin] prepare release HikariCP-2.3.0-rc3
10 years ago
e3d3adf79a
[maven-release-plugin] rollback the release of HikariCP-2.3.0-rc3
10 years ago
89ddc3f948
[maven-release-plugin] prepare for next development iteration
10 years ago
8e7d7fddd2
[maven-release-plugin] prepare release HikariCP-2.3.0-rc3
10 years ago
3fbcbf87b5
When resetting the network timeout to its original value we can avoid an additional call to
...
getNetworkTimeout() by adding a specialized version of the method.
10 years ago
f7aa730e86
Based on input from other developers, we can be sure that currentTimeMillis() will never retrograde (at the resolution the housekeeper runs).
10 years ago
6f0659d4e4
Add check to housekeeping thread to handle backward flow of time.
10 years ago
a386815d7e
Revert "Use System.nanoTime() instead of System.currentTimeMillis() almost everywhere. System.currentTimeMillis() can go backwards!"
...
This reverts commit 01bebb5d35
10 years ago
01bebb5d35
Use System.nanoTime() instead of System.currentTimeMillis() almost everywhere. System.currentTimeMillis() can go backwards!
10 years ago
3a681fccff
Improve ConcurrentBag coverage.
10 years ago
843808bec1
Coverage changes trying to get coveralls.io to work with the new project configuration
10 years ago
d6d0f4909d
Update code coverage plugin version.
10 years ago
ac7268f3c3
Minor cleanup.
10 years ago
0323a7dacb
Let PoolUtilities use its own executor. Sharing executors can lead to deadlocks (not observed, but theoretical)
10 years ago
7a0b602dd3
[maven-release-plugin] prepare for next development iteration
10 years ago
de1d3da0e1
[maven-release-plugin] prepare release HikariCP-2.3.0-rc2
10 years ago
3261cc87e3
[maven-release-plugin] prepare for next development iteration
10 years ago
b508990e4e
[maven-release-plugin] prepare release HikariCP-2.3.0-rc1
10 years ago
c9f6d90ab2
Javadoc fixes
10 years ago
0dcef448f6
Prepare for 2.3.0-rc1
10 years ago
590dbf1870
Add some comments. Add evicted check back to housekeeper to cover a rare race condition
...
where the connection is being released at the same time the maxLifetime eviction shedule is
running. That could have allowed the bag entry to be marked evicted, but have the check
in releaseConnection() just missing it, which would result in a maxLifetime connection sitting
in the pool for an indefinite amount of time.
10 years ago
fafa5050ad
Remove maxLifeTime check from getConnection() and use housekeeping scheduler instead.
10 years ago
a4c6c03ded
ConcurrentBag to common code refactor (share code between Java 6/7 and Java 8)
10 years ago
d47d5a7b0e
Fix #207 Make PoolUtilities stateful, because using statics causes issues when two pools with different drivers and different capabilities exist in the same JVM. Pull out non-pooly things into a separate utility class.
10 years ago
7e7d124a93
Bump revision number due to large internal refactor.
10 years ago
87be723621
Issue #206 suppress noisy exceptions in "quiteSleep()" method.
10 years ago
a6152f58a9
Merge more common code. Benchmarks are showing no negative impact so far.
10 years ago
688d1911e2
Merge more common code. HikariConfig is not a critical class, but we need to be careful about what we merge due to performance implications of inheritance and virtual dispatch that cannot be optimized by the JIT.
10 years ago
ce6d72dd00
Remove some redundant code and inaccurate comment.
10 years ago
9d486abbfa
Massive structure refactor. Make IDE setup hell, but greatly improves maintainability.
10 years ago
82f98fc57e
Project restructuring experiment
10 years ago
d304c511b3
Be careful coding while drinking.
10 years ago
b84727e4c9
Use execute() instead of submit() for the addConnectionExecutor.
10 years ago
527c8ce59c
Issue #206 Throw an exception if the bag is closed, this will cause addConnection() to cleanly close the opened connection and correctly decrement the pool count.
10 years ago
396ecf4008
Somewhere along the way we lost our override of isClosed()...
10 years ago
ce515ac3b8
Scrub, scrub. A little cleaner.
10 years ago
855dbafb86
Cleanup pool suspend/resume semaphore use, add unit test.
10 years ago
560f6e402a
Minor cleanup. Make isUseJdbc4Validation final.
10 years ago
e78d68e65f
Cleaner still, rolls back totalConnection() increment, and sets last connection failure.
10 years ago
949bff3997
Even cleaner connection test check.
10 years ago
66118ff4c4
Minor cleanup. Listener is never null.
10 years ago
501db5ab6e
Cognitive load shift.
10 years ago
Brett Wooldridge