Error message for NoSQL Workbench starting DynamoDB Local is incorrect

Question

Not a question, but an issue report. When starting DynamoDB Local in NoSQL Workbench 3.13.6 (macOS 15.6) I get the error message:
> Java Runtime Environment (JRE) version 11.x or newer is required for running DynamoDB local.

However, my main Java version installed was already 11:
> ~ java --version
> openjdk 11.0.27 2025-04-15
> OpenJDK Runtime Environment Homebrew (build 11.0.27+0)
> OpenJDK 64-Bit Server VM Homebrew (build 11.0.27+0, mixed mode)

Then checking the `dynamoDB-local.log` file makes it clear that Java 17 is actually the minimum version required:
> {
>  message: 'Error: LinkageError occurred while loading main class com.amazonaws.services.dynamodbv2.local.main.ServerRunner
' +
>    '	java.lang.UnsupportedClassVersionError: com/amazonaws/services/dynamodbv2/local/main/ServerRunner has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0
',
>  level: 'error',
>  timestamp: '2025-09-22T02:54:51.815Z'
>}

Class version 61 equates to Java 17, not 11.

The error message should be updated to reflect the correct version. Thanks.

re:Post Agent · Answer

You're absolutely right about this discrepancy. The error message in NoSQL Workbench is indeed incorrect. While NoSQL Workbench displays an error message stating that "Java Runtime Environment (JRE) version 11.x or newer is required for running DynamoDB local," the actual requirement for recent versions of DynamoDB local is JRE version 17.x or newer.

This is confirmed by the error in your log file, which shows a class file version compatibility issue. The class file version 61.0 corresponds to Java 17, while your Java 11 installation (which produces class file version 55.0) is insufficient despite meeting what the error message claims is required.

For DynamoDB local version 2.6.0 or greater, Java 17.x or newer is required, not Java 11.x as the error message suggests. This requirement change likely occurred with newer versions of DynamoDB local, but the error message in NoSQL Workbench hasn't been updated to reflect this change.

To resolve this issue, you would need to install Java 17 or newer on your system. After upgrading your Java version, NoSQL Workbench should be able to successfully start DynamoDB local using the GUI toggle.  
**Sources**  
[Download NoSQL Workbench for DynamoDB - Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/workbench.settingup.html)  
[Deploying DynamoDB locally on your computer - Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html)  
[Connecting to live datasets - Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/workbench.querybuilder.connect.html)  
[[macOS] NoSQL Workbench DynamoDB Local unable to start via GUI on/off switch because it cannot find an SDKMAN-managed JDK | AWS re:Post](https://repost.aws/questions/QUN6K9PHdUQuW6kTd1zraENg/macos-nosql-workbench-dynamodb-local-unable-to-start-via-gui-on-off-switch-because-it-cannot-find-an-sdkman-managed-jdk)

Error message for NoSQL Workbench starting DynamoDB Local is incorrect

Füge deine Antwort hinzu

Relevanter Inhalt