Driver validation during execute_statement delays library path validation #362
Labels
Comments
kares
added a commit
to kares/logstash-input-jdbc
that referenced
this issue
Jan 21, 2020
resolves logstash-plugins#369 (also related logstash-plugins#362)
This was referenced Jan 21, 2020
kares
added a commit
to logstash-plugins/logstash-integration-jdbc
that referenced
this issue
Jan 22, 2020
these are non-critical improvements for (input) driver loading. issues are kept on the original repo since they concern the plugin. this is expected to resolve logstash-plugins/logstash-input-jdbc#369 (also partially relates to logstash-plugins/logstash-input-jdbc#362)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The plugin only loads the driver(s) during open_jdbc_connection, that is executed with execute_statement.
Because of this, if the file passed to jdbc_driver_library doesn't exist, an error only happens when the scheduler triggers for the first time.
Also, the execute_statement adquires the connection_lock but if the open_jdbc_connection raises an exception the lock isn't released, causing logstash to deadlock during shutdown in close_jdbc_connection
The text was updated successfully, but these errors were encountered: