-
Notifications
You must be signed in to change notification settings - Fork 76
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
Comments
…ed to connect to Standalone V8 VM\n"
also #72 |
Thanks you for the quick response. |
Please give info about environment. And if you have already solved the problem, then what was the reason |
Reminder from http://www.nodeclipse.org/#support SupportBrowse existing questions on StackOverflow, as we do.
Should you report a bug, please include the following: example #78 |
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. |
sorry,it does not make very sense ,wrong typo |
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
|
OS WIN7/64 Eclipse Standard 4.3.1 step to reproduce. |
thanks very much for help |
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 |
What is your Java version? Do you mean the solution was to run |
java version "1.6.0_30" yes,the solution is to run node --debug-brk app.js first. |
That is interesting. Then maybe #72 was also not about java, but something that should trigger inside Node |
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" |
Nodeclipse 0.9.0 is just released http://www.nodeclipse.org/ Welcome to update |
hi,paul.how do i upgrade nodeclipse from 0.8.0 to 0.9.0. |
i already click the button "Check for updates",it got nothing to update |
that is because every version has it's own update p2 site. check http://www.nodeclipse.org/ |
I still cannot get it to work my js file is simple `
`
But then V8 fails. I am not sure where I need to make the changes. Below is the error I get.
I am using Node: v8.1.0 and Eclipse Version: Neon.3 Release (4.6.3) Build id: 20170314-1500 Any suggestions? |
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 Already set up Debug configuration with argument "--inspect-brk". Any help much appreciate it! |
Closing this issue, create new for any questions and reference #107 |
One such ticket is #220 There are many reasons why this message can be seen, so raise detail issue. |
node --debug-brk app.js
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.The text was updated successfully, but these errors were encountered: