2 Answers
- Newest
- Most votes
- Most comments
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.
answered 4 years ago
Relevant content
- asked a year ago
- asked a year ago
- asked 3 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago