Repository navigation
[SUREFIRE-2294] [REGRESSION] Debugging failsafe tests: Message "Listening for transport dt_socket at address" is written too late #2613
Description
Wolfgang Knauf opened SUREFIRE-2294 and commented
I launch integration tests with this command: "mvn -Pmyprofile -Dmaven.failsafe.debug verify"
With 2.22.2, it prints a message "Listening for transport dt_socket at address: 5055" and then stops:
!debug_test_mvn_listening_2222.png!
With 3.5.2, it stops after the line "TESTS":
!debug_test_mvn_listening_352.png!
Â
The line "Listening for transport dt_socket at address: 5055" is written AFTER a debugger was attached. This is a bit too late, and it might confuse newbie users that don't know what is happening here and why it hangs.
Attachments:
- debug_test_mvn_listening_2222.png (149.44 kB)
- debug_test_mvn_listening_352.png (94.61 kB)
Activity
olamy commentedon Jul 23, 2025
issue introduced with 3.0.0-M5
culprit c5319bf
gagashaggy commentedon Apr 3, 2026
Please fix this bug. In our project, we encountered this problem (not being able to attach the debugger from the console window in IntelliJ IDEA because the message doesn't appear) after switching from JUnit 4 to JUnit 5. We were using version 3.2.5 and at first we didn't know the reason, but then we found this bug. So we had to roll back to the last version where this message appears normally (3.0.0-M5). But it turned out to cause another problem: now test logs appear in console all together after the test ends, but during test the logs are empty and it looks like the test is not doing anything. We use junit-jupiter 5.10.1, junit-platform 1.10.1 and cucumber 7.15.0, but changing their versions (updating or downgrading) doesn't help, only updating maven-surefire-plugin helps, but then this bug returns.
WolfgangHG commentedon Apr 5, 2026
@gagashaggy I think this bug does not prevent attaching the debugger (at least for Eclipse), you just have to attach it when maven stops printing output. Or does IntelliJ rely on parsing the maven output?
gagashaggy commentedon Apr 5, 2026
@WolfgangHG It does not prevent, of course, you can attach it by running an additional debug configuration, but it is less convenient than just clicking the Attach debugger caption in the console log, which we have used for several years.
Issue #2613 Debugging failsafe tests: Message 'Listening for transpor…
Issue #2613 Debugging failsafe tests: Message 'Listening for transpor…
olamy commentedon May 19, 2026
fixed
WolfgangHG commentedon Jun 2, 2026
I can confirm that it works with 3.5.6. @olamy Many thanks for fixing this!