Added parameter initalizationMaxAttempts which controls number of att…

[kny78]

…empts to connect to the database. See issue 770: #770

[coveralls]

Coverage decreased (-0.2%) to 76.474% when pulling 2c27a23 on polpot78:dev into fe4f68a on brettwooldridge:dev.

[brettwooldridge]

@polpot78 Thanks for the pull request.

We decided to solve the problem in a slightly different way (e3b79ee and 7bab1a8). The change is to introduce a new property initializationFailTimeout while at the same time deprecating the initializationFailFast property. We'd prefer to avoid a net increase in configuration properties.

Setting initializationFailTimeout=0 mimics initializationFailFast=true. Setting initializationFailTimeout=Long.MAX_VALUE (or any significantly long period) mimics initializationFailFast=false. And of course, setting a relatively short period (eg. minutes or hours) will likely achieve what you were looking for.

[kny78]

Thanks, This will solve our problem! Do you have a timeline for when it will be released? Regards, Kjetil Nygård

On Mon, 2016-11-28 at 17:41 -0800, Brett Wooldridge wrote: @polpot78 Thanks for the pull request. We decided to solve the problem in a slightly different way (e3b79ee and 7bab1a8).  The change is to introduce a new property initializationFailTimeout while at the same time deprecating the initializationFailFast property.  We'd prefer to avoid a net increase in configuration properties. Setting initializationFailTimeout=0 mimics initializationFailFast=true.  Setting initializationFailTimeout=Long.MAX_VALUE (or any significantly long period) mimics initializationFailFast=false.  And of course, setting a relatively short period (eg. minutes or hours) will likely achieve what you were looking for. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.       {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5 5493e4bb","name":"GitHub"},"entity":{"external_key":"github/brettwool dridge/HikariCP","title":"brettwooldridge/HikariCP","subtitle":"GitHu b repository","main_image_url":"https://cloud.githubusercontent.com/a ssets/143418/17495839/a5054eac-5d88-11e6-95fc- 7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent .com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed- b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/brettwooldridge/HikariCP"}},"update ***@***.*** in #771: @polpot78 Thanks for the pull request.\r\n\r\nWe decided to solve the problem in a slightly different way (e3b79ee and 7bab1a8).  The change is to introduce a new property ``initializationFailTimeout`` while at the same time deprecating the ``initializationFailFast`` property.  We'd prefer to avoid a net increase in configuration properties.\r\n\r\nSetting ``initializationFailTimeout=0`` mimics ``initializationFailFast=true``.  Setting ``initializationFailTimeout=Long.MAX_VALUE`` (or any significantly long period) mimics ``initializationFailFast=false``.  And of course, setting a relatively short period (eg. minutes or hours) will likely achieve what you were looking for.\r\n"}],"action":{"name":"View Pull Request","url":"#771# issuecomment-263451334"}}}

--  Regards,    Kjetil Nygård    +47 4147 4337    polpot78@gmail.com