Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-29000

Debugger does not work for quarkus project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • 4.28.0.Final
    • 4.28.0.AM1
    • quarkus
    • None
    • Sprint #238, Sprint #239, Sprint #240
    • 3
    • Hide

      1. Open Quarkus perspective
      2. File -> New Quarkus project -> Type: Maven, name: "testdebug" -> Finish
      3. Open "ExampleResource.java" in "src/main/java/org.acme/" -> add some "System.out.println("TEST");" before return -> place a brake point on this line
      4. Right click on project -> Debug as -> Debug configuration... -> Double click on "Quarkus Application" -> Debug
      5. Open "localhost:8080/hello" in browser -> see console output in Eclipse

      Expected: No new output, highlighted "System.out
      .println("TEST");" -> click "Step over" -> "TEST" printed to console output
      Now: "Test" printed to output, application is not paused. Behavior as for "Run As".

      NOTE: 
      1. Debug WORKS fine during the Integration tests (Jenkins and local via "mvn clean verify ..."). There is a normal behavior.
      2. Debug DOESN'T work if IT runs via Eclipse (Right click on test -> Run as -> Reddeer test) or during manual testing.

      Show
      1. Open Quarkus perspective 2. File -> New Quarkus project -> Type: Maven, name: "testdebug" -> Finish 3. Open "ExampleResource.java" in "src/main/java/org.acme/" -> add some "System. out .println( "TEST" );" before return -> place a brake point on this line 4. Right click on project -> Debug as -> Debug configuration... -> Double click on "Quarkus Application" -> Debug 5. Open "localhost:8080/hello" in browser -> see console output in Eclipse Expected: No new output, highlighted "System.out .println( "TEST" );" -> click "Step over" -> "TEST" printed to console output Now: "Test" printed to output, application is not paused. Behavior as for "Run As". NOTE:   1. Debug WORKS fine during the Integration tests (Jenkins and local via "mvn clean verify ..."). There is a normal behavior. 2. Debug DOESN'T work if IT runs via Eclipse (Right click on test -> Run as -> Reddeer test) or during manual testing.
    • Workaround Exists
    • Hide

      workaround is to run manually the java remote debugger by creating new launch configuration > Debug as Launch mode / Remote Java Application as Launch Configuration Type > click Next Then Browse the correct Project if not selected, and select the correct Port that is displayed in the console, then click Finish. 

      Show
      workaround is to run manually the java remote debugger by creating new launch configuration > Debug as Launch mode / Remote Java Application as Launch Configuration Type > click Next Then Browse the correct Project if not selected, and select the correct Port that is displayed in the console, then click Finish. 
    • ---

      Debug as -> Quarkus configuration does not work

              stephane.bouchet Stephane Bouchet
              rh-ee-olkornii Oleksii Korniienko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: