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

Server adapter: "Start/Restart in Debug" is broken for Nodejs

    XMLWordPrintable

Details

    • devex #128 February 2017
    • Hide
      1. ASSERT: have a nodejs application running in OpenShift, the project imported to your workspace and a server adapter created for it.
      2. EXEC: pick your server adapter for your nodejs application and choose "Restart in Debug" or "Debug" (depending on if the adapter already is started or not) from the context menu

      Result:

      You get an error popping up that tells you that your server adapter could not be launched.
      In the Eclipse log you'll spot the following:

      java.lang.IllegalArgumentException: port out of range:-1
	at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
	at java.net.InetSocketAddress.<init>(InetSocketAddress.java:224)
	at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory.connectToStandalone(JavascriptVmEmbedderFactory.java:193)
	at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.StandaloneV8LaunchType.createConnectionToRemote(StandaloneV8LaunchType.java:30)
	at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:69)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

      Notice how the server adapter is in debugging state even though the debugger is not launched/attached:

      Show
      ASSERT: have a nodejs application running in OpenShift, the project imported to your workspace and a server adapter created for it. EXEC: pick your server adapter for your nodejs application and choose "Restart in Debug" or "Debug" (depending on if the adapter already is started or not) from the context menu Result: You get an error popping up that tells you that your server adapter could not be launched. In the Eclipse log you'll spot the following: java.lang.IllegalArgumentException: port out of range:-1 at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143) at java.net.InetSocketAddress.<init>(InetSocketAddress.java:224) at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory.connectToStandalone(JavascriptVmEmbedderFactory.java:193) at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.StandaloneV8LaunchType.createConnectionToRemote(StandaloneV8LaunchType.java:30) at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:69) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Notice how the server adapter is in debugging state even though the debugger is not launched/attached:

    Attachments

      Issue Links

        causes

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-24183 OpenShiftDebugUtilsTest: #testGetDebuggingContext is failing

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        is caused by

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-22362 Server Adapter: Static changes done to nodejs application are not visible

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed
        is incorporated by

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-24083 Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed
        is related to

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-23422 Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-24184 Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        relates to

        Feature Request - Feature requests from customers and/or users JBIDE-24016 Server adapter, integration tests: assert debugging scenarios

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-22066 Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Pull Request Sent

        Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-23900 Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Activity

          People

            adietish@redhat.com André Dietisheim
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: