How to set the ignite driver offline in DBeaver tool

[shibaditi]

Hi All, We are using ignite 2.9.1 sdk for our project. We are also using dbeaver tool to view the ignite cache data. During installation dbeaver its download the ignite package from internet but we don't want to download from internet as our customer are not ready to allow internet connection on those servers.

are there any offline dbeaver tool which will not look internet for package download ?
How can set the driver setting for ignite in dbeaver in stead of download package from internet ? see below image

We are facing this below issue in some of environments , Could anyone help on this ?

Thanks

[LonwoLonwo]

Hello @shibaditi

You can upload your driver manually in the "Edit Driver Settings" on the "Libraries" tab.
Maybe it can help you.

[shibaditi]

Thanks @LonwoLonwo for your help. I have tried adding those files like below screen shot but it seems to be not working.. still its claiming no driver installed and trying to download from internet.

But when the driver installed by downloading from internet by tool , its looks like below.

So not sure what I'm missing here

[LonwoLonwo]

Have you tried to delete the original driver path from the libraries list?

[shibaditi]

Thank You @LonwoLonwo . It worked. Here is the below screen look like after remove that default package

[yanxg]

Is there any list about which drivers needed for apache ignite? I download annotations-16.0.3.jar cache-api-1.0.0.jar ignite-core-2.12.0.jar ignite-shmem-1.0.0.jar It still complains that can't load driver class 'org.apache.ignite.IgniteJdbcThinDriver'

[shibaditi]

Hi Yanxg,

not sure which ignite pakage version you are using. I am sharing for version 2.9.1. You can download from the below

Download the Ignite Core 2.9.1 drivers and its dependency drivers from the side :
Main link there you can find all drivers for 2.9.1 version :
https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.9.1 .

Or

Download below listed drivers for 2.9.1 version
ignite-core-2.9.1.jar
cache-api-1.0.0.jar
annotations-16.0.3.jar
ignite-shmem-1.0.0.jar

If you are not using 2.9.1 verion then install first ignite drivers through online and then find out the drivers list installed under driver folder or dbeaver UI. Then try to download all those drivers seperately from internet or copy those driver from folder.

[yanxg]

Hi Shibaditi @shibaditi Thank you for your answer. I am using the ignite 2.12.0 and DBeaver 22.0.4 and the system is Mac mini M1 11.5.1

All the drivers are downloaded manually. My MacBook Air can successfully download drivers and run DBeaver for ignite but not the Mac mini M1.

Though all of those drivers are also under /Library/DBeaver/drivers, it still shows cannot find them

[LonwoLonwo]

Can you provide a full log error message?

[yanxg]

@LonwoLonwo Thanks. The .log message for one attempt launch is

!SESSION 2022-05-17 12:05:53.560 -----------------------------------------------
eclipse.buildId=unknown
java.version=17
java.vendor=Eclipse Adoptium
BootLoader constants: OS=macosx, ARCH=aarch64, WS=cocoa, NL=en_NZ
Framework arguments:  -keyring /Users/username/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch aarch64 -keyring /Users/username/.eclipse_keyring

!ENTRY org.eclipse.e4.ui.workbench 4 0 2022-05-17 12:05:54.627
!MESSAGE Unable to retrieve the bundle from the URI: bundleclass://com.dbeaver.ee.runtime.ui/com.dbeaver.ee.runtime.internal.ui.LicenseStartupAddon

!ENTRY org.jkiss.dbeaver.model 4 0 2022-05-17 12:06:31.683
!MESSAGE Error creating driver 'Apache Ignite' instance.
Most likely required jar files are missing.
You should configure jars in driver settings.

Reason: can't load driver class 'org.apache.ignite.IgniteJdbcThinDriver'
!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2022-05-17 12:06:31.683
!MESSAGE Error creating driver 'Apache Ignite' instance.
Most likely required jar files are missing.
You should configure jars in driver settings.

Reason: can't load driver class 'org.apache.ignite.IgniteJdbcThinDriver'
!SUBENTRY 2 org.jkiss.dbeaver.model 4 0 2022-05-17 12:06:31.683
!MESSAGE ExceptionInInitializerError
!STACK 0
java.lang.ExceptionInInitializerError
	at org.apache.ignite.internal.util.IgniteUtils.<clinit>(IgniteUtils.java:878)
	at org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:312)
	at org.apache.ignite.internal.IgniteVersionUtils.<clinit>(IgniteVersionUtils.java:94)
	at org.apache.ignite.IgniteJdbcThinDriver.<clinit>(IgniteJdbcThinDriver.java:140)
	at java.base/java.lang.Class.forName0(Native Method)
	at java.base/java.lang.Class.forName(Unknown Source)
	at org.jkiss.dbeaver.registry.driver.DriverDescriptor.loadDriver(DriverDescriptor.java:1121)
	at org.jkiss.dbeaver.registry.driver.DriverDescriptor.loadDriver(DriverDescriptor.java:1059)
	at org.jkiss.dbeaver.registry.driver.DriverDescriptor.getDriverInstance(DriverDescriptor.java:635)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.getDriverInstance(JDBCDataSource.java:687)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.openConnection(JDBCDataSource.java:124)
	at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.openConnection(GenericDataSource.java:137)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.connect(JDBCExecutionContext.java:103)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.initializeMainContext(JDBCRemoteInstance.java:100)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.<init>(JDBCRemoteInstance.java:59)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.initializeRemoteInstance(JDBCDataSource.java:113)
	at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.<init>(GenericDataSource.java:109)
	at org.jkiss.dbeaver.ext.generic.model.meta.GenericMetaModel.createDataSourceImpl(GenericMetaModel.java:90)
	at org.jkiss.dbeaver.ext.generic.GenericDataSourceProvider.openDataSource(GenericDataSourceProvider.java:106)
	at org.jkiss.dbeaver.registry.DataSourceDescriptor.openDataSource(DataSourceDescriptor.java:983)
	at org.jkiss.dbeaver.registry.DataSourceDescriptor.connect(DataSourceDescriptor.java:920)
	at org.jkiss.dbeaver.runtime.jobs.ConnectJob.run(ConnectJob.java:70)
	at org.jkiss.dbeaver.runtime.jobs.ConnectionTestJob.run(ConnectionTestJob.java:103)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.RuntimeException: java.nio.DirectByteBuffer.address field is unavailable.
	at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1570)
	at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1557)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at org.apache.ignite.internal.util.GridUnsafe.bufferAddressOffset(GridUnsafe.java:1557)
	at org.apache.ignite.internal.util.GridUnsafe.<clinit>(GridUnsafe.java:109)
	... 25 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field long java.nio.Buffer.address accessible: module java.base does not "opens java.nio" to unnamed module @7ef0519f
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(Unknown Source)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(Unknown Source)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Unknown Source)
	at java.base/java.lang.reflect.Field.setAccessible(Unknown Source)
	at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1562)
	... 29 more

Interestingly, the java here shows the java.version = 17 and it comes from Eclipse Adoption. But when I go to terminal java --version, it shows openjdk 11.0.15 2022-04-19 LTS which is assumed to use since the ignite uses java 11. Meanwhile, wondering whether a downloaded community beaver is kinda of bounded to a computer? Since when I uninstall the DBeaver in /Applications and redownload the community version and install, it is surprising that it does not attempt to download driver and the driver settings the same as the uninstalled one, and it throws the error immediately.