dynamodb local: ERROR StatusLogger Log4j2 could not find a logging implementation

前端 未结 4 476
面向向阳花
面向向阳花 2021-01-04 04:51

This is the first time that this issue has occurred to me, I have used DynamoDB local on Linux and Mac and most of the time it worked fine, and now I\'m on a different Mac m

相关标签:
4条回答
  • 2021-01-04 05:11

    How I got this to work is to do the following:

    Extract the contents of the jar file to a seperate folder

    jar xf DynamoDBLocal_Orig.jar
    

    Add the following to the pom.xml

    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-to-slf4j</artifactId>
        <version>${log4j.version}</version>
    </dependency
    

    Edit the META-INF/MANIFEST.MF file and add

    DynamoDBLocal_lib/log4j-core-2.13.3.jar
    

    Compress to a new jar

    jar cmvf META-INF/MANIFEST.MF DynamoDBLocal.jar *
    

    Rename DynamoDBLocal.jar from the base folder to DynamoDBLocal_old.jar

    Move the newly created DynamoDBLocal.jar to the base folder.

    Download the log4j-core-2.13.3.jar from https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core/2.13.3

    Place the log4j-core-2.13.3.jar inside the DynamoDBLocal_lib folder

    Run

    java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
    
    0 讨论(0)
  • 2021-01-04 05:13

    According to this AWS Support Forum response by an AWS person this problem doesn't affect the working of the DynamoDB local instance.

    They do intend to fix it so that the messages isn't displayed but it doesn't make a functional difference.

    I haven't yet managed to make my local instance work but there may be other, un-associated, issues with that.

    0 讨论(0)
  • 2021-01-04 05:20

    It seems like zip versions are corrupted. You can download .rar file, it will work. .rar has log4j-core-2.8.jar along with Log4j-api-2.x.jar inside the DynamoDBLocal_lib folder and it is working for me.

    0 讨论(0)
  • 2021-01-04 05:29

    I just had exactly the same problem. I tried both the tar and the zip file from Europe (frankfurt) region. The problem persisted. I can see the log4j-core package in the classpath, but somehow it doesn't get picked up. Not sure if the other AWS regions are corrupted too.

    I solved it by asking a colleague of mine to share his DynamoDB folder. He downloaded it a few months ago, and it's working like a charm.

    Solution: AWS needs to fix the package, otherwise see if you can ask a colleague to help you out.

    0 讨论(0)
提交回复
热议问题