Nodeclipse / nodeclipse

Nodeclipse-1 : Eclipse plugin for Node.js, PhantomJS development (Nodeclipse core plugin); Maven and Gradle (with Android) plugins
https://nodeclipse.github.io/
158 stars 78 forks source link

Failed to connect to Standalone V8 VM (2014) use `node --debug-brk app.js` #107

Closed haroldjiang closed 6 years ago

haroldjiang commented 10 years ago

when debug js file in eclipse,the ide prompt with "Failed to connect to Standalone V8 VM"

UPDATE:

solution is

to run node --debug-brk app.js first.

paulvi commented 10 years ago

http://www.nodeclipse.org/#support

paulvi commented 10 years ago

also #72

haroldjiang commented 10 years ago

Thanks you for the quick response.

paulvi commented 10 years ago

Please give info about environment. And if you have already solved the problem, then what was the reason

paulvi commented 10 years ago

Reminder from http://www.nodeclipse.org/#support

Support

Browse existing questions on StackOverflow, as we do.

haroldjiang commented 10 years ago

thanks for you tip of searching in stackflow.i did it as http://stackoverflow.com/questions/8615226/eclipsenode-js-error-when-debugging-failed-to-connect-to-standalone-v8-vm-con told.

then it works.it does make very sense to me.i wish it can be like debug java in eclipse(.just debug as java application in ide).why do we need debug it in command line first,and then we can debug in eclipse.

haroldjiang commented 10 years ago

sorry,it does not make very sense ,wrong typo

paulvi commented 10 years ago

Question http://stackoverflow.com/questions/8615226/eclipsenode-js-error-when-debugging-failed-to-connect-to-standalone-v8-vm-con is not related to Nodeclipse directly.

Check #72, the reason may be Java version incompatibly.

Please give

haroldjiang commented 10 years ago

OS WIN7/64 Eclipse Java Development Tools 3.9.1 Eclipse PlatForm 4.3.1 nodeclipse - http://dl.bintray.com/nodeclipse/nodeclipse/0.8.0/

Eclipse Standard 4.3.1

step to reproduce. 1 right click on the main node js file.it prompts out with a dialog. 2 choose "Debug AS Node Application" 3 get a message of "Failed to connect to Standalone V8 VM Connection refused: connect"

haroldjiang commented 10 years ago

thanks very much for help

haroldjiang commented 10 years ago

by the way after run "node --debug-brk app.js" in command lin first.then do those steps above,you wont get the error message.it works as expecation

paulvi commented 10 years ago

What is your Java version?

Do you mean the solution was to run node --debug-brk app.js first?

haroldjiang commented 10 years ago

java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

yes,the solution is to run node --debug-brk app.js first.

paulvi commented 10 years ago

That is interesting. Then maybe #72 was also not about java, but something that should trigger inside Node

haroldjiang commented 10 years ago

yeah,maybe.if click "Debug AS Node Application" without running node --debug-brk app.js first,always get the error message of "Failed to connect to Standalone V8 VM Connection refused: connect"

paulvi commented 10 years ago

Nodeclipse 0.9.0 is just released http://www.nodeclipse.org/

Welcome to update

haroldjiang commented 10 years ago

hi,paul.how do i upgrade nodeclipse from 0.8.0 to 0.9.0. if i install 0.9.0 directly in "Install New Software" of Eclipse.will it override the old version. thanks in advance.

haroldjiang commented 10 years ago

i already click the button "Check for updates",it got nothing to update

paulvi commented 10 years ago

that is because every version has it's own update p2 site. check http://www.nodeclipse.org/

rajivkanaujia commented 7 years ago

I still cannot get it to work

my js file is simple

`
var http = require("http");

// create a http server that writes hello world
http.createServer(function(request, response) {

    // Send the HTTP header 
    // HTTP Status: 200 : OK
    // Content Type: text/plain
    response.writeHead(200, {
        'Content-Type' : 'text/plain'
    });

    // Send the response body as "Hello World"
    response.end('Hello World\n');
}).listen(8081);

//Console will print the message
console.log('Server running at http://127.0.0.1:8081/');

` When I try to debug this as a Node Application, I get following at Eclipse Console

Debugger listening on ws://127.0.0.1:5858/b1bdf38d-c53a-472d-89f8-6819c5e4c8b1 For help see https://nodejs.org/en/docs/inspector

But then V8 fails. I am not sure where I need to make the changes. Below is the error I get.

Nodeclipse/chromedevtools failed to connect to Standalone V8 VM ( Check Help (F1) and Support http://www.nodeclipse.org/#support ) . Info: Timed out waiting for handshake

I am using Node: v8.1.0 and Eclipse Version: Neon.3 Release (4.6.3) Build id: 20170314-1500

Any suggestions?

bryanpham85 commented 7 years ago

Seem the issue has been solved somewhere, however I'm still facing this issue with Eclipse Oxygen + Nodeclipse. Constantly got this error message "Failed to connect to Standalone V8 VM Timed out waiting for handshake"

Already set up Debug configuration with argument "--inspect-brk".

Any help much appreciate it!

paulvi commented 7 years ago

Closing this issue, create new for any questions and reference #107

paulvi commented 6 years ago

One such ticket is #220

There are many reasons why this message can be seen, so raise detail issue.