search

cagataygurturk / lambadaframework

Build serverless REST API's with JAVA. It implements the JAX-RS API and deploys your application easily to AWS Lambda and API Gateway
MIT License
243 stars 50 forks source link

Internal Server Error - trying example #37

Open freedev opened 7 years ago

freedev commented 7 years ago

Just trying the boilerplate, may I have any help in order to understand what's happened?

Invoking function... ==================== FUNCTION OUTPUT ==================== {"errorMessage":"Internal Server Error"} ==================== FUNCTION LOG OUTPUT ==================== START RequestId: 24dafee1-a6fc-11e6-9f4b-ebdfce24d81b Version: $LATEST log4j:WARN No appenders could be found for logger (org.lambadaframework.runtime.Handler). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. END RequestId: 24dafee1-a6fc-11e6-9f4b-ebdfce24d81b REPORT RequestId: 24dafee1-a6fc-11e6-9f4b-ebdfce24d81b Duration: 1315.60 ms Billed Duration: 1400 ms Memory Size: 512 MB Max Memory Used: 87 MB

refacktor commented 5 years ago

There is some underlying issue with exception logging in the lambada request handler. It doesn't log all (or maybe any) exceptions. I encountered this in my own code. You may have have to fork the boilerplate and add your own try/catch block and log the exception yourself to figure out what's going on. If you are working with the boilerplate code as-is, the most likely issue is either permissions or you failed to update the Bucket and Region names to match your needs.