Skip to content

Log server output and thread dump when the test framework server fails to start #55363

Description

@ahus1

Task Description

When the test framework's DistributionKeycloakServer fails to start or does not become ready within the timeout, the test only fails with Server did not become ready within 120 seconds, and the managed server is killed without any further information. The managed server's output is only forwarded at WARN level and above, so the CI log contains nothing that explains why the server did not start. This was seen in the Windows CI job (Java Distribution IT/UT, windows-latest, temurin 27), where JavaKeystoreKeyProviderTest failed because the server did not become ready, while the rerun of the same test started the server in about 25 seconds.

On a failed startup, and before the server process is killed, the test framework should log a report with the state of the process and its child processes, all output of the server since it was started (including INFO level and stderr), and a thread dump of each running Java process. The thread dump should be taken with jcmd, as sending a signal to trigger it is not available on Windows.

Example of such a failure, from #55349: https://github.com/keycloak/keycloak/actions/runs/44527074676/job/135572124532

Activity

  1. added a commit that references this issue on Nov 19, 2026
    8c2ea77
  2. added theissue type on Nov 19, 2026
  3. self-assigned this
    on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Fields

No fields configured for task.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions