You can translate the question and the replies:

Slf4j dependency conflict changing to "Insufficient resources to execute operation" when trying to connect Dremio as a JDBC datasource

Hi, I'm currently running Denodo Platform v7.0 on Windows. I'm attempting to connect Dremio as a JDBC datasource and running into errors when testing the connection. I have added the Dremio JDBC driver .jar file to a new directory in the {DENODO HOME}/lib-external/jdbc-drivers directory. I'm using the following configurations when attempting to connect: Database adapter: Generic Driver class path: '/home/denodod/DenodoInstallers/denodo-platform-7.0/lib-external/jdbc-drivers/dremio-jdbc-driver/dremio-jdbc-driver-2.0.5-201806021755080191-767cfb5.jar' Driver class: com.dremio.jdbc.Driver Database URI: **Dremio URI Here** Transaction isolation: Database default Initially I was getting the following exception: *Internal error: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of com/denodo/util/ZipClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature * However, after attempting to test the connection twice, the error message changed to the following: *Unable to establish connection: Insufficient resources to execute operation* I did not change any configurations or take any other actions that might have directly caused the change in error message. Any idea what could be causing this problem, or how to resolve it? I can provide the stack traces from the vdp-admin.log file if need be. Thanks!
user
29-01-2019 13:26:44 -0500
code

3 Answers

Hi, I created your scenario and found that there are some dependencies mismatch caused by the Log4j library included within this Dremio driver. The Log4j library usually causes problems when it is used in applications with different class loaders and different versions of the library are loaded. Since the Denodo Platform already includes a Log4j library I would recommend you to unzip the Dremio jdbc driver (.jar file) and delete the Slf4j folder from the org folder. Test your connection with the modified .jar file. Hope this helps!
Denodo Team
13-02-2019 03:49:39 -0500
code
Hi, thanks for your response. The issue was partially with the Slf4j folder and also with the org/apache/logging folder. When both folders were removed from the Dremio JDBC driver jar, Denodo was able to successfully connect to Dremio
user
13-02-2019 08:21:43 -0500
Hi, I am glad you are able to connect Dremio from Denodo. The additional step to remove logging folder helps.
Denodo Team
04-04-2019 07:04:38 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here