Open benjamin-confino opened 2 months ago
In this case I'm not sure how the arquillian container would know that liberty is running in debug mode since the OpenLiberty Telemetry 2.0 TCK test is starting the server before running the arquillian tests.
Do you know whether it's possible to query whether a liberty server has a debugger attached? It might be possible to implement this if we can query that information from an mbean or something.
Otherwise, I suggest you increase the verifyAppDeployTimeout
in the arquillian.xml. This file can reference system properties, so if you know that you've started the server in debug mode, it would be possible to pass through a much longer value for the deploy timeout.
Also note that in most cases, it should now be ok to have a fairly long deploy timeout. liberty-arquillian will notice if the app fails to start so the timeout will only be used if the app hangs while starting.
Issue Overview
When debugging a problem during application startup liberty-arquillian timed out and killed my server
Expected Behaviour
The code that checks for timeouts can tell if Liberty is started in debug mode and will not timeout
Current Behaviour
Liberty-arquillian kills the server during a middle of a debug session.
Steps To Reproduce
I'll put the exact steps I did.
./gradlew :io.openliberty.microprofile.telemetry.2.0.internal_fat_tck:buildandrun -Ddebug.server
in an open liberty workspaceAdditional Information