Windows: UnsatisfiedLinkError in latest release (JNI symbol missing), works on WSL/Linux

[jorisrs]

Hi,

I’m seeing a Windows-specific issue with the latest TileDB-Java release. On native Windows, TileDB fails to load the JNI bindings with:

dec 17, 2025 4:53:58 P.M. io.tiledb.libtiledb.NativeLibLoader loadNativeTileDB
WARNING: Could not load Native TIleDB
dec 17, 2025 4:53:59 P.M. io.tiledb.libtiledb.NativeLibLoader loadNativeTileDBJNI
WARNING: Could not load Native TileDB JNI

java.lang.UnsatisfiedLinkError: 'long io.tiledb.libtiledb.tiledbJNI.new_tiledb_config_tpp()'

	at io.tiledb.libtiledb.tiledbJNI.new_tiledb_config_tpp(Native Method)
	at io.tiledb.libtiledb.tiledb.new_tiledb_config_tpp(tiledb.java:717)
	at io.tiledb.java.api.Config.<init>(Config.java:68)

This happens consistently on Windows, but the same code works without errors on WSL (Ubuntu).

Environment

• OS: Windows 10 22H2
• Java: Temurin JDK 21
• TileDB-Java version: 0.29.0 and 0.30.0, (0.28.1 DOES work on Windows)
• Works on: WSL Ubuntu (same Java version)

Additional note: the latest GitHub release (0.30.0) does not appear to be published to Maven Central.

Please let me know if you’d like me to test a snapshot or provide additional diagnostics.
Thanks in advance!

[tdbbyd]

Hi @jorisrs ,

Thank you for opening this issue.

I wanted to let you know that the latest release, TileDB-Java 0.31.0, has now been published to Maven Central.

Regarding the Windows-specific issue: we have tested the latest version on native Windows and, so far, we have not been able to reproduce the JNI loading failure you’re seeing. To help with verification, I’ve attached a minimal Maven project that runs successfully against TileDB-Java 0.31.0 and has been tested on Windows.

If you’re able to try this project on your setup, it may help narrow down whether the issue is environment-specific.

Best regards

TileDBWindowsExample.zip

[jorisrs]

Hi @tdbbyd ,

Thank you for your response. I can confirm that the minimal project does indeed run on my machine. I see that the specified SDK is Microsoft OpenJDK 17. Switching to Eclipse Temurin 17 resulted in the same error. Same goes for java 21, the Microsoft SDK works, but the Temurin SDK does not.

For now the (temporary?) fix seems to be switching to Microsoft OpenJDK 21. Could you tell us if support for Temurin will be fixed in the future?

Thanks!