generated from micronaut-projects/micronaut-project-template
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Micronaut Tracing 4.5.0 causing Starvation #229
Comments
Hi @driverpt Can you try to use Micronaut core Thanks :) |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
AWS API Gateway Lambda Requests to work
Actual Behaviour
We're getting 503 Service Unavailable.
By analysing the Logs we notice that the Controllers are properly invoked and returned but after that the request just becomes a ghost.
Micronaut 4.4.0 doesn't work with Micronaut 3.8.1. See here for more information
Workaround: Downgrade Micronaut to 3.7.5 and Micronaut Tracing to 4.4.0.
Steps To Reproduce
micronaut-function-aws-api-proxy
lambda_provided
Runtime to AWS LambdaEnvironment Information
Example Application
No response
Version
3.8.1
The text was updated successfully, but these errors were encountered: