Datomic Knowledgebase - Recent questions tagged dependencies

Datomic peer on dynamodb - misleading error message

Fri, 13 Feb 2026 16:19:56 +0000

Starting from a simple setup:

{:deps {com.datomic/peer       {:mvn/version "1.0.7491"}
        org.slf4j/slf4j-simple {:mvn/version "2.0.17"}}}

And trying to connect into a dynamodb connection, it fails with a "s3" error:

user=> (require '[datomic.api :as d])
nil
user=> (d/connect "datomic:ddb://us-east-1/prd/db")
[main] INFO datomic.process-monitor - {:event :metrics/initializing, :metricsCallback clojure.core/identity, :phase :begin, :pid 311, :tid 3}
[main] INFO datomic.process-monitor - {:event :metrics/initializing, :metricsCallback clojure.core/identity, :msec 0.696, :phase :end, :pid 311, :tid 3}
[main] INFO datomic.process-monitor - {:metrics/started clojure.core/identity, :pid 311, :tid 3}
[clojure-agent-send-off-pool-0] INFO datomic.domain - {:event :cache/create, :cache-bytes 502267904, :pid 311, :tid 25}
[clojure-agent-send-off-pool-0] INFO datomic.process-monitor - {:AvailableMB 895.0, :ObjectCacheCount 0, :event :metrics, :pid 311, :tid 25}
Execution error (ClassNotFoundException) at jdk.internal.loader.BuiltinClassLoader/loadClass (BuiltinClassLoader.java:580).
com.amazonaws.services.s3.model.MultiObjectDeleteException

From this error message, it is pretty hard to find that datomic actually requires an extra dynamodb dependency to work.

https://docs.datomic.com/operation/storage.html#dynamodb-aws-peer-dependency

Possible fixes:

A better error message
Adding this error message to datomic docs, as a "common errors" - do google will be able to find.

Datomic on JDK25 - WARNING: A restricted method in java.lang.System has been called

Fri, 13 Feb 2026 16:19:55 +0000

Using this dependencies

{:deps {com.datomic/peer                    {:mvn/version "1.0.7491"}
        org.slf4j/slf4j-nop                 {:mvn/version "2.0.17"}
        com.amazonaws/aws-java-sdk-dynamodb {:mvn/version "1.12.564"}}}

Note: aws-java-sdk-dynamodb has an updated version, but 1.12.564 is the recommended

Generate these warnings:

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by io.netty.util.internal.PlatformDependent0$4 (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)
WARNING: Please consider reporting this to the maintainers of class io.netty.util.internal.PlatformDependent0$4
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::loadLibrary has been called by io.netty.util.internal.NativeLibraryUtil in an unnamed module (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

This issue report focus in the first part:

WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::loadLibrary has been called by io.netty.util.internal.NativeLibraryUtil in an unnamed module (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)

Trace:
- io.netty/netty-common 4.1.100
- required by org.apache.activemq/artemis-commons 2.31.2
- required by org.apache.activemq/artemis-core-client 2.31.2
- required by com.datomic/peer.

Datomic on JDK25 - WARNING: A terminally deprecated method in sun.misc.Unsafe has been called

Fri, 13 Feb 2026 16:19:51 +0000

Using this dependencies

{:deps {com.datomic/peer                    {:mvn/version "1.0.7491"}
        org.slf4j/slf4j-nop                 {:mvn/version "2.0.17"}
        com.amazonaws/aws-java-sdk-dynamodb {:mvn/version "1.12.564"}}}

Note: aws-java-sdk-dynamodb has an updated version, but 1.12.564 is the recommended

Generate these warnings:

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by io.netty.util.internal.PlatformDependent0$4 (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)
WARNING: Please consider reporting this to the maintainers of class io.netty.util.internal.PlatformDependent0$4
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::loadLibrary has been called by io.netty.util.internal.NativeLibraryUtil in an unnamed module (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

This issue report focus in the first part:

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by io.netty.util.internal.PlatformDependent0$4 (file:/root/.m2/repository/io/netty/netty-common/4.1.100.Final/netty-common-4.1.100.Final.jar)

Trace:
- io.netty/netty-common 4.1.100
- required by org.apache.activemq/artemis-commons 2.31.2
- required by org.apache.activemq/artemis-core-client 2.31.2
- required by com.datomic/peer.