[jlouvel]

Refs #1601.

SecurityTestCase sometimes gets Communication Error (1001) instead of a 401/403 in CI. The client logs only the final IOException, and only at FINE, which CI doesn't enable, so we can't see which step fails. This PR doesn't fix the failure. It makes the next one diagnosable.

Changes

• NettyClientHelper logs at FINE each connection:

  • opened
  • reused from the pool
  • discarded because inactive
  • returned to the pool or closed (with the reusable flag)
  • closed (from its close future)

• NettyClientCall logs at FINE:

  • each request sent
  • each response head received (with the status)
  • each response end received
  • each exchange failure, with its cause

  Every message includes the Netty channel, which shows the id and the local and remote ports. The messages are suppliers, so they cost nothing when FINE is off.

• org.restlet/pom.xml: new ci-logging profile. It points the default-test execution to src/test/ci-logging.properties. That config keeps the console at INFO, and writes the FINE logs of the org.restlet loggers to org.restlet/target/restlet-fine.log.

• build.yaml: the build uses -P default,test,ci-logging. When the build fails, a new step uploads the log and the surefire reports as the test-logs artifact.

• changes.md: entry under Misc.

Notes

• Local full run of org.restlet with the profile: the log is 1.8 MB, about 15k lines.
• ShutdownHookTestCase.whenServerIsHandlingBlockingRequestThenItRefusesNewRequest failed locally on Windows, with and without the profile. Its ±200 ms timing tolerance is too tight on this machine, so the failure is unrelated to this change. All 2214 other tests passed.
• Setting java.util.logging.config.file turns Engine.configureLog() into a no-op for those test runs. No test depends on it: ConnectorTestCase only sets the INFO level, which the config already uses.

How to read a failure

Download the test-logs artifact, then search restlet-fine.log for the port in the failing test's URI (R:localhost/127.0.0.1:<port>). The sequence shows whether the request went on a reused connection, whether the response head arrived, and when the connection closed relative to the failure.

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

The new log runs before the completed-exchange guard, causing normal HTTP/2 and HTTP/3 stream teardown to emit misleading failure messages and stack traces after successful exchanges.

1 open issue

• Log failures only after the completed-exchange guard · New

What changed in this PR

This PR adds diagnostics for intermittent HTTP client failures tracked in #1601. It expands Netty logging and preserves CI test logs for investigation; it does not fix the underlying failure.

Changes:

• Adds FINE logs for connection lifecycle events and request/response exchanges.
• Introduces a CI logging profile that writes detailed Restlet logs while keeping console output at INFO.
• Uploads logs and test reports after CI failures and documents the change.

File	Description
org.restlet/​src/​test/​ci-logging.properties	Configures INFO console output and FINE file logging.
org.restlet/​src/​main/​java/​org/​restlet/​engine/​netty/​NettyClientHelper.java	Logs connection creation, reuse, pooling, and closure.
org.restlet/​src/​main/​java/​org/​restlet/​engine/​netty/​NettyClientCall.java	Logs request sending, response receipt, and exchange failures.
org.restlet/​pom.xml	Adds the ci-logging test profile.
changes.md	Records the new diagnostics and CI log retention.
.github/​workflows/​build.yaml	Enables CI logging and uploads diagnostic artifacts on failure.

_{Review effort: Balanced}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud