Java was started but returned exit code=1073807364 - eclipse

I am using STS, jdk 1.6. It was working fine until now. I am getting this STS pop-up when I start it.
Java was started but returned exit code=1073807364
C:/jdk1.6.0_18/bin/javaw.exe
-Dosgi.requiredJavaVersion=1.5
...
... /15 more lines of stack on the pop-up window.
Any idea?

Found this; Looks like there is no one problem, that error code can come from a variety of events.
From what I can tell, this error code (0x40010004) arises in all sorts of situations, with (as you noted) no obvious common thread.
However this page says "0x40010004" means "the task is running"! So, I would surmise that the correct way to interpret it is as saying "this tasked has exited in a way that prevented it setting a proper exit code".
I don't know if this will help, but I would try looking in the Windows Event logs to see if the problem is being reported there.
found here: What is the cause of JVM exit code 1073807364?

From my experience, that error (described as "task is running") occurs when there is a thread in blocking mode, and the thread cannot be terminated by being interrupted (per the rules) so it lingers, causing the program to hang, and requiring a kill shot. I have experienced that error as recently as today (Sept 5, 2012), and that was the cause (because I did it deliberately).
There may be other causes, but that is one distinct possibility.

All I can suggest is updating your JDK to the latest release (1.6.0_23) and STS to the latest version (2.5.2) and seeing if the problem still persists.

Related

How can I debug why eclipse won't start?

I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log

Why does eclipse close by itself while running?

It's been happening lately for some unknown reason.I have the latest version of Eclipse ADT (25 Sept 2014) and it just shuts off while I'm working. Any ideas?
Start Eclipse from a terminal to see the standard output. Chances are that the Java VM runs into a problem because of SWT which can crash the VM. Note: If you're using Windows, you may have to use java.exe instead of javaw.exe to get output.
Also look into the Error Log. Eclipse has a view for that or look into the file .../workspace/.metadata/.log The file might contain an error message.
If you find an error in either the console or the error log, let us know and we might be able to help.
The issue could also be because of the JVM that was chosen for the project.

Bug DBGp Response Error: error code 206

I have used Xdebug of Eclipse 3 months so far. And it runs really well.
However, I got a issue of Xdebug which is "DBGp Response Error: eval:=206 msg:error evaluating code" ( in Error Log).
After I investigate the error, I find that issue is:
206 - Error evaluating code (use from eval() (or perhaps property_get
for a full name get))"
This is reference from http://xdebug.org/docs-dbgp.php
I have taken 2 days for this issue, and nothing has changed.
Please help me solve this. Many thanks and strong appreciation for your help.
Try deleting your watches. You can read the story of how this worked for me in PHPStorm.
It is probably an eval that (your IDE) is doing wrong. Either the symbol does not exist, or the syntax is incorrect. I am not sure where your error_log comes from (do you mean xdebug.remote_log?), but that will also indicate what eval command was sent by the IDE. If you could amend your question with the exact log lines before and after your 206 error too, I can give a better clue. In general, this isn't much of an issue, as it's often not possible to eval specific code.
CentOS 7.7
PHP 7.2 and PHP 7.4
Apache and cli
Same symptoms " The strange in here is that it has run well, and suddenly can not debug with those things in error log" as #ndnguyen
Worked great. Then suddenly didn't work without explanation. I tried updating everything, several different config options, etc, etc.
Just that stupid little check box. FYI: The IDE is vscode.

What could cause EasyEclipse to terminate with error window?

When I start EasyEclipse, I get error:
JVM terminated. Exit code=127
Do you have any idea as to the possible cause for this kind of error message?
If this happen right from the start, it may be related to your eclipse.ini content.
See this one (for Eclipse 3.6 Helios),
and check the end of each lines of your eclipse.ini: there should be no extra space.
After that, it depends on:
the exact Eclipse version
the exact JVM used to launch said Eclipse
your platform (OS)
See for instance bug 174642.

Hot Code Replace Failed (eclipse)

"Hot Code Replace Failed - add method not implemented".
I get this error message every time I change something in my test class (and save it).
Can't figure out what it means. Can somebody help?
Possibly, you have a test which is still running (in debug mode). Try finishing all tests (you can see them in the debug view: window->show view->debug) and try again...
See this thread:
This means you changed a class while it was debugging an application and it could not update the class for the application while it was running.
The error suggests you may be running an older JVM, i.e. pre-1.4.2 but this error can occur with any JVM if the change is incompatible with the previous version of the class.
Check carefully what JRE you are using in your debug session.
Also check you are deploying classes compiled with the debug attribute set. (see this thread)
Finally, as indicated here:
did you switch "Project->Build Automatically" off?
Hot code replacement works (only?) if automatic build is switched on...
I was running into this issues too. I found a build hiding in the backgound that was giving me fits. Check to make sure you have all tests/builds closed or completed. Nonetheless, you can still run the new code.
Whenever this error message appears it also gives options to terminate or restart. Select Terminate and it will terminate any running debug case which you are unable to locate.
if you have multiple projects involved, and multiple jre's installed, make sure all dependent projects are using the same javac/jre
Make sure your application server JRE and Eclipse JRE version should be same or else it will throw unsupported class version and hot code debug will not work.
I went to the same Problem,But my Debugging session ended hours ago.But still ECLIPSE error kept coming.
So I just simply restart the ECLIPSE IDE, then the problem just solved.