apache5-connector currently depends on httpclient5 5.3.1. While troubleshooting a misbehaving application today, I figured out the root cause was that httpclient5 had been bumped to 5.4 by another transitive dependency. Observed behavior is that some calls end up with a SocketReadTimeoutException.
I then tried to bump httpclient5 to 5.4 in Jersey repo and run mvn -T1C package -pl connectors/apache5-connector for both 2.45 and 3.1.9 which resulted in multiple test failures. All tests pass when running with 5.3.1.
I have not yet figured the root cause of the regression.
It would be nice to address this issue in next Jersey release to ensure that clients can safely use latest httpclient5.
apache5-connector currently depends on httpclient5 5.3.1. While troubleshooting a misbehaving application today, I figured out the root cause was that httpclient5 had been bumped to 5.4 by another transitive dependency. Observed behavior is that some calls end up with a SocketReadTimeoutException.
I then tried to bump httpclient5 to 5.4 in Jersey repo and run
mvn -T1C package -pl connectors/apache5-connector
for both 2.45 and 3.1.9 which resulted in multiple test failures. All tests pass when running with 5.3.1.I have not yet figured the root cause of the regression.
It would be nice to address this issue in next Jersey release to ensure that clients can safely use latest httpclient5.