-
Notifications
You must be signed in to change notification settings - Fork 187
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
Make timeouts configurable #62
Comments
Sequel supports various vendor-specific and connection-pool-specific options that were not exposed to the plugin. This change introduces a dedicated new configuration option to set a timeout and also a catch-all configuration option for any other options that Sequel supports upon opening a new database connection. Fixes logstash-plugins#62.
Sequel supports various vendor-specific and connection-pool-specific options that were not exposed to the plugin. This change introduces a dedicated new configuration option to set a timeout and also a catch-all configuration option for any other options that Sequel supports upon opening a new database connection. Fixes logstash-plugins#62.
Sequel supports various vendor-specific and connection-pool-specific options that were not exposed to the plugin. This change introduces a dedicated new configuration option to set a timeout and also a catch-all configuration option for any other options that Sequel supports upon opening a new database connection. Fixes logstash-plugins#62. Fixes logstash-plugins#64
Thanks for the quick turnaround on this @talevy ! |
There is an issue in this PR which I can reproduce. With the plugin updated (and even without specifying the new jdbc connection pool timeout property), it is failing at sequel/adapters/jdbc.rb:216:
If I hardcode the password string instead of
|
Currently, the timeouts (I think?) are hard-coded within Sequel to be 5 seconds. It could be useful to have this be configurable.
The text was updated successfully, but these errors were encountered: