mattcasters commented on PR #11645: URL: https://github.com/apache/nifi/pull/11645#issuecomment-5587040916
I think the failure on `system-tests / ubuntu-24.04 Java 21` is caused by github and not the code changes I made: ``` Started Server on https://localhost:5670/nifi ERROR [main] org.apache.nifi.runtime.Application Start Server failed java.io.UncheckedIOException: Management Server start failed Caused by: java.net.BindException: Address already in use ``` Jetty bound HTTPS on 5670, then the management server (standalone tests use 127.0.0.1:56730 in bootstrap.conf) could not bind. NiFi shut itself down. The test client then waited 5 minutes, got connection refused, and reported “Failed to start NiFi”. Why it is unrelated to this PR • The hang is a port conflict on the management server, not Parameter Context merge. • Flow load had already succeeded (Successfully synchronized dataflow… Process Groups=0). • ParameterContextPreservationIT (the tests added in this PR) passed (8 tests, ~3s) later in the same job. • macos-15 Java 21/25 and the other Ubuntu jobs passed. The previous class, ContentClaimTruncationAfterRestartIT, uses isAllowFactoryReuse() = false and restarts NiFi. If that process (or a leftover standalone) still held 56730, the next standalone instance fails exactly this way. That is a known Linux CI flake under load (TIME_WAIT / leftover PID), not something this PR introduced. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
