[jbosstools-issues] [JBoss JIRA] (JBIDE-23961) Server adapter: "Restart in Debug" is broken for Nodejs

Andre Dietisheim (JIRA) issues at jboss.org
Thu Feb 16 18:11:00 EST 2017


     [ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-23961:
-------------------------------------
    Steps to Reproduce: 
# 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" from the context menu

Result:
!image-2017-02-16-23-30-21-709.png! 
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:
{code}
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)
{code}

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

 !server-adapter-erroneous-debugging-state.png! 

  was:
# 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" from the context menu

Result:
!image-2017-02-16-23-30-21-709.png! 
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:
{code}
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)
{code}

Notice how the server adapter is in debugging state even though the debugger is not launched/attached
 !server-adapter-erroneous-debugging-state.png! 



> Server adapter: "Restart in Debug" is broken for Nodejs
> -------------------------------------------------------
>
>                 Key: JBIDE-23961
>                 URL: https://issues.jboss.org/browse/JBIDE-23961
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.3.Final
>            Reporter: Andre Dietisheim
>            Priority: Critical
>         Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list