All Versions
44
Latest Version
Avg Release Cycle
51 days
Latest Release
187 days ago

Changelog History
Page 1

  • v25.0

    November 30, 2019
    • Catching-up with vibur-object-pool version 25.0.
  • v24.0

    November 29, 2019
    • 🛠 Fixed https://github.com/vibur/vibur-dbcp/issues/13 - problem with SQL queries parameters logging when inputs are not integers.
    • ♻️ Minor other refactoring.
    • Catching-up with vibur-object-pool version; skipped version 23.0 for vibur-dbcp.
  • v22.2

    May 05, 2018
    • 🐎 Small performance update.
  • v22.1

    March 30, 2018
    • Adopted changes / improvements from Vibur Object Pool 22.1.
    • ♻️ Various other small improvements, refactoring, and javadoc updates.
  • v22.0

    February 08, 2018
    • ➕ Added logLineRegex configuration option - the application can use this option in conjunction with the logTakenConnectionsOnTimeout option in order to filter the generated stack trace lines.
    • ➕ Added takenConnectionsFormatter configuration option - allows the application to implement custom formatting to String of the TakenConnection[] array. Note that the default formatter uses the logLineRegex for filtering.
    • ➕ Added GetConnectionTimeout programming hook that is invoked only if the call to DataSource.getConnection() timeouts. The application can use this hook to format and redirect the generated taken-connections log to a different than the usual log location, for example, to Amazon S3. Note that in order to enable the taken-connections tracking the application must set poolEnableConnectionTracking to true. The default hook uses the takenConnectionsFormatter; it can be disabled via setting logTakenConnectionsOnTimeout to false.
    • 🛠 Fixed a bug in the CloseConnection hook takenNanos parameter calculation, before its value was sometimes incorrect.
  • v21.3

    January 28, 2018
    • 🛠 Fixed a minor bug in the ResultSet size calculation where the size was sometimes calculated off by one.
  • v21.2

    November 29, 2017
    • 🛠 Fixed a bug in the implicit closing of the current ResultSet functionality, introduced in version 21.0.
    • 🛠 Fixed a rarely occurring bug related to the possibility of Statement.getResultSet() to return null.
  • v21.1

    November 27, 2017
    • ➕ Added resultSetNanoTime parameter to the ResultSetRetrieval programming hook. This parameter complements the existing resultSetSize parameter and represents the total time taken to iterate over and process the retrieved ResultSet.
  • v21.0

    November 24, 2017
    • 🚚 Moved the getConnection() retry mechanism (for lazily created connections) from the ConnectionFactory level to the PoolOperations level - this improves the connections reuse in certain situations.
    • Implemented implicit closing of the current ResultSet when the parent Statement is closed.
    • 🔄 Changed some configuration defaults: a) poolInitialSize 10 -> 5; b) poolMaxSize 100 -> 50; c) reducerTimeIntervalInSeconds 60 -> 30; d) reducerSamples 20 -> 15; e) connectionTimeoutInMs 30_000 -> 15_000; f) acquireRetryDelayInMs 1000 -> 500;
    • Adopted changes / improvements from Vibur Object Pool 21.0.
    • ♻️ Various other small fixes, refactoring and improvements.
  • v20.0

    September 26, 2017
    • 🔄 Changed the behavior of getConnection(...) to throw an SQLException("...interrupted while getting SQL connection...") when the current thread is interrupted; it was throwing an SQLTimeoutException before. The thread interrupted status remains set / uncleared as it was before.