You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a Quarkus Run/Debug Application launch configuration the quarkus project runs fine, but if you run in debug mode Eclipse throws an error even though the debugger seems to have already connected. In fact, it seems like the debugger connects whether you choose either Run or Debug, so you don't need to use the debug launch configuration at all?
Although not blocking I can verify this occurs to me as well. In my case I debugged the code and i found out the following:
Using:
m2e-core: 1.20.1
Quarkus tools 4.24
I found that the error message is produced due to multiple attempts to attach to the debug port:
One attempt is made by QuarkusLaunchConfigurationDelegate:
if ("debug".equals(mode)) {
createRemoteJavaDebugConfiguration(configuration, debugPort, monitor);
}
The other attempt(s) are made by m2e-core. More specifically MavenConsoleLineTracker reads messages printed to the console and when it finds lines matching the expression "Listening for transport dt_socket at address: (\d+)$", it automatically tries to launch a Remote Java Application debug session.
As a result one of the attempts succeeds and therefore debugging works fine, but the other attempts fail and cause the error message(s)
With a Quarkus Run/Debug Application launch configuration the quarkus project runs fine, but if you run in debug mode Eclipse throws an error even though the debugger seems to have already connected. In fact, it seems like the debugger connects whether you choose either Run or Debug, so you don't need to use the debug launch configuration at all?
Looks like the debug connection is already established by Eclipse, so https://github.com/jbosstools/jbosstools-quarkus/blob/main/plugins/org.jboss.tools.quarkus.core/src/org/jboss/tools/quarkus/core/launch/QuarkusLaunchConfigurationDelegate.java#L92 can't connect?
Copy of error
The text was updated successfully, but these errors were encountered: