eclipse-ee4j / eclipse-ee4j/jersey

JdkConnector does not properly cleanup ERROR state connections

Open
#5,599 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
730
Forks
382
PR merge metrics
No merged PRs in 30d

Description

I am using Dropwizard 4 (Jersey 3.0.5) on Java 17. This problem exists in 3.0.12 as well.

When an HttpConnection transitions to ERROR from IDLE state, the connection gets closed but not removed from DestinationConnectionPool. This results in the next request failing regardless of whether the server has been restarted.

My guess is that cleanClosedConnection should be called at: https://github.com/eclipse-ee4j/jersey/blob/fc78757d0b2ece3f03e2c35f709fe070c350fc96/connectors/jdk-connector/src/main/java/org/glassfish/jersey/jdk/connector/internal/DestinationConnectionPool.java#L287

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.