DynamoDB Local not starting because Log4j2 logging implementation error

0

When I try to start DynamoDB locally I get an error related to Log4j2. I've tried the dynamodb_local_latest.tar.gz and the docker compose installations both resulting with the console output shown below.

Initializing DynamoDB Local with the following configuration:
Port: 8000
InMemory: false
DbPath: null
SharedDb: true
shouldDelayTransientStatuses: false
CorsParams: *

ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

munizas
asked 4 years ago415 views
2 Answers
1

Hi,

Recently we had upgraded log4j-api to newer version and removed the log4-core which is giving this error message. It does not affect the behavior of DynamoDB Local, so you should not have any issues other than this message got printed in the screen and local should still be working as expected. However to get rid off this message, will notify team to assess and add log4j-core with binary in future release.

Thanks,
Zoe

answered 4 years ago
0

Thanks for your response Zoe! Yeah it's working fine, I was thrown off by the error so I didn't even bother to try and interact with the database. Thanks again.

munizas
answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions