Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
haroldjiang opened this issue Jan 2, 2014 · 23 comments
Closed
Labels

Comments

@haroldjiang
Copy link

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
Copy link
Member

paulvi commented Jan 2, 2014

paulvi added a commit to Enide/nodeclipse-1 that referenced this issue Jan 2, 2014
@paulvi
Copy link
Member

paulvi commented Jan 2, 2014

also #72

@haroldjiang
Copy link
Author

Thanks you for the quick response.

@paulvi
Copy link
Member

paulvi commented Jan 2, 2014

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

@paulvi
Copy link
Member

paulvi commented Jan 2, 2014

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

Support

Browse existing questions on StackOverflow, as we do.

  • How do I? -- 1) F1/Help -> Help Contens -> Nodeclipse Help , 2) Online Help or 3) StackOverflow!
  • I got this error, why? -- StackOverflow!
  • I got this error and I'm sure it's a bug -- raise an issue!
  • Should you report a bug, please include the following:

    1. Nodeclipse version number (like 0.5 or 0.6)
    2. Eclipse version number (like 4.2.2 or 3.8.0)
    3. Eclipse distribution (e.g. Eclipse for JEE Developers)
    4. A detailed description of the steps necessary to reproduce the problem.
    5. Screenshot and stack trace, that you can get from Eclipse Error Log View (Window -> Show View ...) or from '.log' file from the directory '.metadata' in your workspace.
    6. See example issue #78

    example #78

@haroldjiang
Copy link
Author

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
Copy link
Author

sorry,it does not make very sense ,wrong typo

@paulvi
Copy link
Member

paulvi commented Jan 3, 2014

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

  • Nodeclipse version number (like 0.5 or 0.6)
  • Eclipse version number (like 4.2.2 or 3.8.0)
  • Eclipse distribution (e.g. Eclipse for JEE Developers)
  • A detailed description of the steps necessary to reproduce the problem.

@haroldjiang
Copy link
Author

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
Copy link
Author

thanks very much for help

@haroldjiang
Copy link
Author

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
Copy link
Member

paulvi commented Jan 3, 2014

What is your Java version?

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

@haroldjiang
Copy link
Author

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
Copy link
Member

paulvi commented Jan 3, 2014

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

@haroldjiang
Copy link
Author

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
Copy link
Member

paulvi commented Jan 3, 2014

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

Welcome to update

@haroldjiang
Copy link
Author

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
Copy link
Author

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

@paulvi
Copy link
Member

paulvi commented Jan 5, 2014

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

@rajivkanaujia
Copy link

rajivkanaujia commented Jun 13, 2017

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
Copy link

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!

@Nodeclipse Nodeclipse deleted a comment from rajivkanaujia Aug 6, 2017
@Nodeclipse Nodeclipse deleted a comment from bryanpham85 Aug 6, 2017
@paulvi
Copy link
Member

paulvi commented Aug 6, 2017

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

@Nodeclipse Nodeclipse locked and limited conversation to collaborators Aug 6, 2017
@paulvi
Copy link
Member

paulvi commented Jan 11, 2018

One such ticket is #220

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

@paulvi paulvi closed this as completed Jan 11, 2018
@paulvi paulvi changed the title Failed to connect to Standalone V8 VM Failed to connect to Standalone V8 VM (2014) use node --debug-brk app.js Jan 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants