I have a very strange issue that I'm hoping someone can help me with. I have various installations of Eclipse on my development machine at work. The one I primarily use is Weblogic WorkSpace Studio 10.2. This installation, along with a few Pulse installations I have set up works fine when I'm logged into my computer physically.
However, when I try to log into the computer using Microsoft's Remote Desktop Connection utility I get an error stating: "Could not create Java virtual machine." and then I get the lovely Eclipse error box which I personally can gather almost nothing from.
Even if you don't have the solution, any help would be greatly appreciated.
Justin
What ended up working for me was the memory settings for the JVM. Apparently the remote desktop connection, or some other setting in Windows, blocks off a fairly large amount of space. By reducing the heap size allocation for the JVM during Eclipse and server start-up I was able to get this working. As a side note, I had PLENTY of space that windows could have used, so I don't think blankly adding more memory would necessarily solve the issue. If you find another solution, please let me know.
• We came across an issue when user RDC’s to a remote system where the OS is Windows 10 and has a running Eclipse instance, the Eclipse instance terminates
• Eclipse is one of the IDE’s for Java
• The issue is because of Windows 10 Exploit protection
• Pre-requisite: You will need Administrative permissions for executing the below
• Navigate to Settings -> Update & Security -> Windows Security -> App & Browser Control -> Exploit Protection Settings
• Add the program to exclude as below
P.s. As of Window 10 1909 MS security advisory mentions we can disable some exploit protections by default.
Perhaps it is permission related. take a look at similar issue that symantec has:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8ea1593f1d1fcee68025759a003d8403?OpenDocument
Try to see if you have same patches installed that causes the security issue. Also refer to application log to see if there is a more specific error. Good luck :)
I think issue happens due to Windows, not Eclipse nor JVM. There is still open Bug report on the Eclipse side and one of the comments state that Microsoft is working on the issue.
I have tried Windows Remote Desktop-ing into my dev machine at work (which had only one version of eclipse installed on it). I had no troubles.
Is it possible that your problems stem from multiple versions of eclipse running at the same time?
Also, have you tried a fresh install of eclipse on your dev machine?
If the above two suggestions don't work, then the only thing that I can think of is what Mohammad said: you might need to check your permissions.
I would check the system log if I were you: Start > run > eventvwr
The first thing to look at is the .log file which is in your eclipse's metadata folder (found in your workspace at $WORKSPACE_ROOT/.metadata/.log). If you post the stack trace that it generates upon initialization, we can give a definitive answer.
I am now experiencing this in Eclipse (the Oxygen release and Java 1.8.0_181). I previously had the same problem with another Java-based program (Oxygen XML/XSL editor - the product name is coincidentally the same as the Eclipse version). Last year the Oxygen support team answered that it may be a known problem in Java.
Even without seeing a crash report, considering your sequence of
events, this seems like a known common cause of crash for the Java
runtime. Keeping Oxygen/Java running for a long time, until the screen
or video card enters sleep then connecting/disconnecting
screens/projectors or connecting/disconnecting RDP can trigger a crash
in the Java runtime. We keep updating the Java runtime (JRE) with each
new version of Oxygen, but so far the issue has not been resolved in
newer versions of the JRE.
e.g. Java VM logged issue:
https://bugs.openjdk.java.net/browse/JDK-8153389
Related
Yes, I know. I got no rep on this site. But I have to ask this.
I upgraded my laptop, my main dev machine, from 14.02 LTS to 14.04 LTS and the plugins I use with eclipse (3.7) completely broke. I use WOLips (https://github.com/wocommunity/wolips) with eclipse. WOLips is for working with WebObjects applications.
I was getting two crashes. One would occur when editing a java file, when auto-suggest kicked in. I fixed this by adding "-Dorg.eclipse.swt.browser.DefaultType=mozilla" to the end of my eclipse.ini. I have no idea how I found that. It took a lot of random searching.
Now, I get an exception whenever I open a WOComponent:
Unhandled event loop exception
No more handles [Could not detect registered XULRunner to use]
Trying to define a XULRunnerPath just gives me even stranger errors.
I can file a bug with eclipse (which I did). I tried eclipse 4.2 and 4.4 and got other complicated integration issues. I can file a bug with mozilla (though I was not aware that they were involved). I can install a copy of xulrunner (outside of my copy of Firefox) and point to that (which I did). I can file a bug with ubuntu launchpad (which I did). None of these get you very much response.
So, I was going from one LTS to another LTS. 14.04 - 14.02 = 0.02. Not a huge deal, yes? Should I have expected problems? How can I file a bug with the people involved in just this upgrade and not the other twelve systems that this touches upon?
I had Apple laptops for a long time. I do not expect that amount of hand-holding. But I do wish someone would throw me a bone.
I can get work done if I go buy another hard disk, install 12.04 onto it and copy all of my data back. Is this really necessary? You know, I am willing to help integration testing of these releases. But the systems for finding the right place to put my oar in the water seem fairly impenetrable. Any suggestions? I do not mind working for a solution. If there is a solution.
Ray,
Did you try Eclipse 4.4 and use the instructions on the wiki for compiling the new WOLips? the Eclipse 4.4 is acting just fine for me (but I'm on a Mac sorry :( )
I have been facing the "Unable to validate Weblogic domain" issue from OEPE for last 2 days. I have tried
(a) downloading and installing different versions of OEPE ;
(b) Using Eclipse and Oracle Weblogic separately ; outside of OEPE etc
It used to work previously and then one day last week, my system shut down unexpectedly and since then I am not able to get Eclipse (irrespective of version) and Weblogic to work together.
I have moved on to using Jboss for the time being. But since my production environment is Weblogic and I would like to use Weblogic for development purposes as well, I am trying to get this issue resolved.
I did search the Oracle and other communities and somebody mentioned its because of difference in java version and to add
-Dsun.lang.ClassLoader.allowArraySyntax=true
in eclipse.ini. My eclipse.ini already has this statement and I still face the issue.Please help.
Iam not the person who answers this question. But the comment above is the answer for this question and it worked for me too. Below is the solution.
I finally got the resolution for this issue. Actually the full credit goes to my colleague, who resolved this bugging bug. Since it drove me crazy, decided that I would spare others from the same experience First of all, there were no errors in any of the logs. Server was starting up but Eclipse did not recognize it as such. And here is the resolution : Go to Window Tab -> Preferences -> General -> Network Connections Change the Active provider to "Direct". The default is usually Native. and that's it. Close and restart eclipse.
It happened to me as well, I even reinstalled weblogic again, after a bit of research I decided to kill the Java(TM) Platform SE Binary process via Task Manager and restarted the Server.
That's all It took to resolve the issue.
I've read the other posts about being unable to install software in eclipse, but I still can't seem to get anything to work. I've tried on both Eclipse Indigo and Eclipse Juno - neither of which seem to be able to connect to anything, yet I can open the web browser.
On my other computer, which was previously configured, it contacts the software sites perfectly fine. I can also use the internal web browser on both version of eclipse - navigating to www.google.com.
I've tried updating Eclipse using http://download.eclipse.org/releases/indigo/ and I have tried to install ADT with https://dl-ssl.google.com/android/eclipse/.
I'm attaching an image of the error I'm getting. Also it appears I am getting 'permission denied'
Regarding the ADT, i couldnt get it to work with indigo for the life of me. After looking around a lot i realized that there are some comparability restrictions for the ADT plug in. The latest version of the ADT works on Eclipse Helios 3.6 or higher.
http://developer.android.com/sdk/requirements.html
also make sure to do "run as administrator" when you start eclipse if you are going to install software.
I had the same problem, I'm not sure if it would help but here is what I did anyway:
Uninstalled AVG
Ran SFC /scannow
SFC found some corrupted windows files and repaired them
Restart
Not sure if uninstalling AVG did anything, but I saw it as a possible solution somewhere else.
I am now using MSE since it seems to be more compatible with my system...
Maybe you need to connect thru a proxy?
Check you browsers connections settings.
I've had the same issue before and it turned out to be due to a VPN connection I had open. It must have been trying to go via that, although no other applications have had that problem. So perhaps check that you don't have any static routes which are interfering.
I have been using Eclipse on Mac OS X from home over a VPN to develop GWT and perl code in a local workspace for my employer. Recently a repeatable and severe lockup began occurring whenever I tried to edit Debug (or Run) launch configurations. I got the spinning beachball of death (SBOD) and, if I waited long enough (10-15 minutes) it would eventually stop and I could at least close the dialog.
I tried numerous things until a coworker suggested trying it with VPN turned off. To my surprise (and somewhat delight) it began behaving normally in the above scenario. I have been using Eclipse in this manner for about a year with no problems so naturally I am racking my brain trying to think of recent changes to VPN and/or to my split tunnel script (euphemistically called 'multihome') that could account for this abnormal behavior. This lockup occurs with or without the split tunnel.
I should also point out that the "initializing Java tooling" progress status ALWAYS occurs when starting eclipse and takes about a minute to complete with VPN connection. Normal (<2 seconds) without.
So, I'm starting to learn how to use wireshark and possibly will look into using packetlogger as well in an attempt to find out more about this strange issue.
Anyone have a clue as to what might be causing this?
This is a hard one to answer. Short answer is "I don't know".
However, I did find out that, due to the recently updated JVM, done as part of the Mac OS X update, Eclipse IDE lost its ability to find the src.jar file for the JRE. As a result, it appears that Eclipse, in various places in the code, searched for this file and when not found attempted to find it via the network. When VPN was turned on, perhaps this exacerbated the problem.
This was solved by fixing the Installed JRE configuration of Eclipse (see JDK on OSX 10.7 Lion).
I thought I'd give Helios a try, so I grabbed the latest Java EE install from http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/heliosr. Note, both OSX 32bit and 64bit exhibit the same symptoms.
So from a fresh install I run Helios (it launches fine), then the problem comes when I try running an upgrade. I keep getting these two errors errors:
Artifact not found: http://download.eclipse.org/releases/helios/compositeContent.jar.
http://download.eclipse.org/releases/helios/compositeContent.jar
No repository found at http://download.eclipse.org/releases/helios.
These are my (default) update sites:
Helios http://download.eclipse.org/releases/helios Enabled
Mylyn for Eclipse Helios http://download.eclipse.org/tools/mylyn/update/helios Enabled
The Eclipse Project Updates http://download.eclipse.org/eclipse/updates/3.6 Enabled
The Eclipse Web Tools Platform (WTP) software repository http://download.eclipse.org/webtools/repository/helios Enabled
http://download.eclipse.org/tools/mylyn/update/e3.4 Disabled
http://download.eclipse.org/tools/mylyn/update/extras Disabled
Note, I'm not behind any firewalls/proxies etc, no nothing weird with network connectivity.
I've searched all over the place and there are others with the same problem, with no solution that I could find.
Has anyone else run into these issues?
UPDATE 1:
Notes:
I'm not behind a proxy.
I've tried the Java EE, but also bare bones Eclipse 3.6.1.
I've tried different mirrors (including the main site),
I've tried SpingSource's version.
I've tried exporting the update sites to XML, deleting them and reimporting them.
I even tried adding forward slashes to the ends of site names.
I've made sure I have full write permissions for the eclipse folder, and have even placed it on my desktop.
I mention all of these seemingly odd behaviours because these are suggestions I've read around the web on this problem, which many people are having.
Once last interesting point I've just tried, is to download the "http://download.eclipse.org/releases/helios/compositeContent.jar" directly in the browser. It redirects to "http://www.gtlib.gatech.edu/pub/eclipse/releases/helios/compositeContent.jar" with a 403 forbidden. :\ It seems as though system is finding a mirror, but perhaps the mirror is broken? Also note, I'm in Australia, so Georgia Tech is nowhere near me ;)
Just as I was writing this, I tried one last idea. I discovered "Pulse" by Genuitec, which is a Eclipse install manager. I gave it a shot, and it worked. The site it uses for updates is:
"[url=http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirror/releases/helios] http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirr or/releases/helios[/url]"
So, I've wasted enough time on this now. I'd create a bug in Eclipse Bugzilla, but there are already entries with no solution.
UPDATE 2:
Ok, from a fresh install, if I disable:
http://download.eclipse.org/releases/helios/
and add Pulse's update site:
http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirror/releases/helios/
I don't get any errors. I really think it's to do with the automatic mirrored update site. Is this possible?
Here is a screenshot of my update sites now:
Regards,
Shane
Ok, I had the same issue on Windows XP 64bits laptop an Fresh Helios 64bits download, however your workaround works for me.
See update 2 in the question.
Shane