Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Multiple concurrent requests causes java lambda containers to fail #154
We are using sam-local locally/in testing to run a java8 lambda with 192MB of memory and a rest endpoint that is called by our application to trigger the lambda.
The api endpoint then returns a 502.
This only happens when multiple java8 lambda containers are run at the same time. If they are triggered in sequence, we do not experience this problem.
This error occurs both with docker for mac (with a memory limit for docker high enough to accomodate the multiple containers) and on linux.
This is a pretty critical problem for us as it means we cannot use the lambdas in local dev or testing.
I am also facing the same issue. If we make multiple concurrent calls, it spins all but one container for sure, which gives an even false impression of concurrency working fine to some extent. I had agree with @Inkromind that it must enforce single invocation if that's what it supports.