Skip to content
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

NPE with Amazon Lambda HTTP with JDK 14 #8575

Closed
gsmet opened this issue Apr 14, 2020 · 4 comments
Closed

NPE with Amazon Lambda HTTP with JDK 14 #8575

gsmet opened this issue Apr 14, 2020 · 4 comments
Labels
area/amazon-lambda kind/bug Something isn't working
Milestone

Comments

@gsmet
Copy link
Member

gsmet commented Apr 14, 2020

Not sure if this is reproducible easily or if it's a race condition.

https://github.com/quarkusio/quarkus/pull/8116/checks?check_run_id=586609694

2020-04-14 18:51:13,557 ERROR [io.qua.ver.htt.run.QuarkusErrorHandler] (vert.x-eventloop-thread-1) HTTP Request to /vertx/hello failed, error id: 52c18190-b23c-4464-b9ef-7d474fc89714-2: java.lang.NullPointerException
	at io.quarkus.it.amazon.lambda.GreetingVertx_RouteHandler_helloPost_2512177757deffeae7730edad0d3de9b1a58d00b.invoke(GreetingVertx_RouteHandler_helloPost_2512177757deffeae7730edad0d3de9b1a58d00b.zig:48)
	at io.quarkus.vertx.web.runtime.RouteHandler.handle(RouteHandler.java:44)
	at io.quarkus.vertx.web.runtime.RouteHandler.handle(RouteHandler.java:15)
	at io.vertx.ext.web.impl.RouteState.handleContext(RouteState.java:1034)
	at io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:95)
	at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:130)
	at io.vertx.ext.web.handler.impl.BodyHandlerImpl$BHandler.doEnd(BodyHandlerImpl.java:296)
	at io.vertx.ext.web.handler.impl.BodyHandlerImpl$BHandler.end(BodyHandlerImpl.java:276)
	at io.vertx.ext.web.handler.impl.BodyHandlerImpl.lambda$handle$0(BodyHandlerImpl.java:87)
	at io.vertx.core.http.impl.HttpServerRequestImpl.onEnd(HttpServerRequestImpl.java:530)
	at io.vertx.core.http.impl.HttpServerRequestImpl.lambda$pendingQueue$1(HttpServerRequestImpl.java:118)
	at io.vertx.core.streams.impl.InboundBuffer.handleEvent(InboundBuffer.java:237)
	at io.vertx.core.streams.impl.InboundBuffer.write(InboundBuffer.java:127)
	at io.vertx.core.http.impl.HttpServerRequestImpl.handleEnd(HttpServerRequestImpl.java:514)
	at io.vertx.core.http.impl.Http1xServerConnection.handleEnd(Http1xServerConnection.java:176)
	at io.vertx.core.http.impl.Http1xServerConnection.handleContent(Http1xServerConnection.java:163)
	at io.vertx.core.http.impl.Http1xServerConnection.handleMessage(Http1xServerConnection.java:140)
	at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:369)

/cc @patriot1burke @evanchooly @oztimpower

@gsmet gsmet added the kind/bug Something isn't working label Apr 14, 2020
@gsmet gsmet added this to the 1.4.0.Final milestone Apr 14, 2020
@quarkusbot
Copy link

/cc @patriot1burke

@matejvasek
Copy link
Contributor

matejvasek commented Apr 14, 2020

I got similar error for Windows JDK 11 JVM Tests and JDK 14 JVM Tests for two different tests.

@matejvasek
Copy link
Contributor

I don't think that this is amazon lambda specific, I've seen it on Quarkus - Vert.x Web - Deployment test. It seems to be quite non-deterministic, maybe some race condition. I wasn't able to reproduce it locally, only on github's CI action.

It looks like io.quarkus.vertx.web.runtime.RouteHandler.initialize() is not called. I tired this. It passed CI 3 times in row, but it still doesn't meant that it is correct.

/cc @mkouba

@mkouba
Copy link
Contributor

mkouba commented Apr 16, 2020

@gsmet @matejvasek This should be addressed by #8579. Unfortunately, I can't "force merge" anymore.

@gsmet gsmet closed this as completed Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/amazon-lambda kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants