-
Notifications
You must be signed in to change notification settings - Fork 559
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
HttpMessageNotReadableException occurs when handling a request. #577
Comments
I am looking at it [Spring Team] |
Thanks @olegz |
Quick update; Based on my current observation it appears that the GraphQl configurations are not picked up. Trying to determine why . . |
@2012160085 for my curiosity do you see the following message in the AWS logs
OR
|
I see the following log from AWS Lambda.
|
closed by mistake. sorry.. |
PR is issued. It was actually the bug in AwsAsyncContext (see commit message). It is also easily reproducible locally again's the code provided by the issue reporter
|
GH-577 Ensure listeners are notified after dispatch
This will be part of 2.0.0-M2 release. Thanks to @olegz for analyzing and fixing the issue. |
I just realised, you can remove the
accidental leftover |
Serverless Java Container version:
2.0.0-M1
Implementations:
Spring Boot 3
Framework version:
SpringBoot 3.1.0
Frontend service:
HTTP API
Deployment method:
Console
Scenario
I've tried to deploy a simple GraphQL API using spring-boot-starter-graphql and aws-serverless-java-conainer-springboot3.
When I run it on a local environment using Tomcat, the request is processed normally. However, when I deploy it on AWS Lambda, I get an org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: No content to map due to end-of-input error.
It seems error occurs while handling request.
I've been trying to solve it for three-full-days, but it hasn't been resolved. Any help would be appreciated.
Expected behavior
200 response should come when a request is sent to http api gateway url using curl.
Actual behavior
An error occurs as shown in the log below.
Steps to reproduce
This is the smallest project repository that can reproduce the error.
https://github.com/2012160085/photomanagement
Full log output
For comparision, local log with Tomcat.
The text was updated successfully, but these errors were encountered: