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: