currently jdbc_driver_path loading is delayed until the first statement is executed,
this means that if a plugin is using schedule a failure in driver loading (such as insufficient read access) will not be visible in the plugin log but only in console.

this is confusing esp. when using LS as a service (console not visible unless journald is inspected) - while LS is self contained its bringing in a driver.jar via this plugin and its not very clear permissions should be taken into account.

plugin should potentially document this + improve its driver.jar checking for read access ...