jersey-netty-connector Stuck eventLoop/ExecuterService threads if Request failed due to invalid header key or value.

[sumitaneja]

NettyConnector doesn't completes/release executorService threads executor and may even lead to stuck evetLoop under stress if headerKey is invalid (say blank) and error happens in netty while validating those. (reproducer attached)

Issue identified in below code with NettyConnector

jersey/connectors/netty-connector/src/main/java/org/glassfish/jersey/netty/connector/NettyConnector.java

Lines 462 to 471 in d9658aa

	jerseyRequest.setStreamProvider(new OutboundMessageContext.StreamProvider() {
	@Override
	public OutputStream getOutputStream(int contentLength) throws IOException {
	replaceHeaders(jerseyRequest, nettyRequest.headers()); // WriterInterceptor changes
	setHostHeader(jerseyRequest, nettyRequest);
	headersSet.countDown();
	return entityWriter.getOutputStream();
	}
	});

Here if any exception happens, below code doesn't get executed leading to stuck executorService threads.

jersey/connectors/netty-connector/src/main/java/org/glassfish/jersey/netty/connector/NettyConnector.java

Line 467 in d9658aa

headersSet.countDown();

This code needs to be fail safe wrapped under try catch with finally countDown the latch.

[sumitaneja]

JerseyNetty.zip

[sumitaneja]

Attached reproducer.

[sumitaneja]

Issue also seen in this error
IlegalArgumentException: Validation failed for header 'Authorization'

This happens when header value is not as per RFC https://www.rfc-editor.org/rfc/rfc9110#name-field-values

for example contains newline.(\n)