Skip to content
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

Disable jdbc4ConnectionTest when connectionTestQuery is set #48

Conversation

praseodym
Copy link
Contributor

Documentation says that jdbc4ConnectionTest is mutually exclusive with the connectionTestQuery property; this commit makes that happen.

brettwooldridge added a commit that referenced this pull request Mar 24, 2014
@brettwooldridge
Copy link
Owner

Mreged into dev.

brettwooldridge added a commit that referenced this pull request Mar 26, 2014
* dev: (77 commits)
  Unwrap DataSource test.
  Discourage users from turning on metrics until they do something useful.
  Add idle fill test.
  Reduce the number of filler threads ... 8 threads is too many on a hyper threaded 4-core CPU.
  Start implementing [optional] metrics for HikariCP.
  Additional connection tests.
  Add provided dependency on coda hale metrics.
  Merged #48 fix connectionTest validation
  Change defaults.
  Default minIdle the same as maxPoolSize.
  Split out stateless utility functions to reduce the weight of the HikariPool class (increases readability).
  Rename idleConnectionBag to connectionBag.
  Change connectionTimeout minimum to 250ms.
  Fix timing edge case in test.
  Check validation error
  Improve warnings for invalid configuration
  Use the DriverManager to create connections.
  Update changes.log.
  Update changes.log.
  Remove deprecated calls from tests, fix test conditions for new background fill behavior.
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants