-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SpringDelegatingLambdaContainerHandler unable to respond with rendered templates #858
Comments
There was an issue with s-c-function-serverless-web. It's been fixed and you can try it by manually upgrading to spring-cloud-function-serverless-web dependency version 4.1.2-SNAPSHOT. |
use spring-cloud-function-serverless-web:4.1.2-SNAPSHOT as advised in aws#858
The PR was merged - 14abccf and function snapshot 4.1.2 is published as well, so technically you just need to use aws-serverless-java-container-springboot3:2.1.0-SNAPSHOT |
Hey @olegz sadly this does not fix the problem... Same symptoms as before
|
Are you sure you get the latest snapshot from s-c-function? Can you try to delete it manually from local repo?
|
Also, make sure you get it fro the right repo - https://repo.spring.io/libs-snapshot-local |
This |
My bad... After |
2.1.0 - That is up to AWS guys, I am just Spring ;) But keep playing with it and see if anything else needs fixing |
Hehe once a spring-cloud-function-serverless-web 4.1.2 release is available, I will be happy to create a 2.0.2 release. 2.1.0 will come somewhere mid/ end of May. |
Ok. Waiting for a fix to be released is easy in comparison to a fix being written 😉 Thank you both |
To help us debug your issue fill in the basic information below using the options provided
Serverless Java Container version:
com.amazonaws.serverless:aws-serverless-java-container-springboot3:2.0.1
Implementations:
Spring Boot
Framework version:
org.springframework.boot:spring-boot-starter-web:3.2.4
Frontend service:
HTTP API / HTML templates
Deployment method:
SAM
Scenario
I want to render HTML (Apache freemarker) Templates within the lambda and send the rendered pages to the client.
Expected behavior
The rendered template is sent to the client.
Actual behavior
After the log messages indicate, that the templates are rendered, nothing happens till the lambda timeouts. This leads to an 500 response from the API Gateway.
Steps to reproduce
Run the sample for the alt-pet-store with these modifications in my fork. Call the link rendered by SAM or make a request for the rout
/index
Side note: The old way as it is used in the pet-store sample (using a
StreamLambdaHandler
) works. You can see this when you apply the patch and deploy thepet-store
sample.Full log output
The text was updated successfully, but these errors were encountered: