Develop Reference

Eclipse JVM error when compiling MCP 9.10 [duplicate]

I am currently running Eclipse on Windows and received an error message I could not decipher:
Unrecognized option: -Xincgc
I have not found any other case of a similar error and could need some help.
I am not sure if I am missing a tool or JRE / JDK.

-Xincgc was an old JVM option that meant, "Use Incremental Garbage Collection." I think it has been deprecated or removed from newer versions of Java. You can probably just delete it. It might be in your Maven .pom file or your Gradle file, or in the build options in Eclipse.

SocketTimeoutException when Ant building in Eclipse

I had been having problems getting Eclipse to build some of my Ant scripts (some built fine, others didn't). Basically, I would get no output in the Eclipse Mars.1 Release (4.5.1) console. My build.xml works fine with ant when I run it on the command line. I was able to find some output in workspace/.metadata/.log where I found the following error message:
!ENTRY org.eclipse.ant.launching 4 120 2016-03-03 09:58:38.197
!MESSAGE Error logged from Ant UI:
!STACK 0
java.net.SocketTimeoutException: Accept timed out
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)
at java.net.ServerSocket.implAccept(ServerSocket.java:545)
at java.net.ServerSocket.accept(ServerSocket.java:513)
at org.eclipse.ant.internal.launching.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:89)
which other people have asked about on Stackoverflow.
The other odd thing I noticed was that there's a line of text right above the console showing which java which shows the version of java being used, and working scripts were different than non-working. Working ant build scripts were using jdk1.7.0_79 whereas failed ones were using the /System installed 1.6.

I don't know why java 1.6 wasn't working for me, but eventually I found where I could change Java for ant builds. It's in Run/External Tools/External Tools Configuration.../<select failing build>/JRE. Oddly, after getting it to work and then trying to switch back to 1.6, it gives me the following message when running ant:
JRE version less than 1.7 is not supported.
so who knows why 1.6 was picked in the first place (maybe the project itself is 1.6) or why it didn't give me a warning!
Anyway, there seems to be several causes of the error I posted above, but here's something you can try.

Have had almost the same problem on Eclipse Oxygen, Java 1.8 and Ant to deploy to tomcat7.
Eclipse’s Console doesn't output any error message. It just says „terminated“ when I clicked Run Ant on the build.xml file. WTF
To solve this I had to set everything to java 1.8 especially ant's runtime JRE . But the „Java Compiler“ -> „Compiler compliance level“ has to be set to java 1.7 only.
Actually it is pretty simple. Well classpath settings can be tricky sometimes ;) especially without any error message.
Do not forget to check your ANT_HOME settings: Eclipse -> Prefs -> Runtime -> „Restore Defaults“ should be sufficient. (Eclipse comes with Ant 1.10.1 as default which requires Java8 at runtime.)
And: If it works for some build.xml-files only you are overriding your workspace settings with your ant-build process. To solve this: Click on „Run As“ -> „Ant Build ... “ (NOT „Ant Build“) and check your classpath (for ant) and the JRE settings here to Java 1.8
Regards
Well simply check your ANT_HOME setting.

Android Studio - Unrecognized VM option 'MaxPermSize=256m'

I just installed Android Studio on Elementary OS 0.3 Freya and run it using the terminal. On my first start-up, however, there's an error message shown:
Gradle 'Test' project refresh failed
Unable to start the daemon process. This problem might be caused by
incorrect configuration of the daemon. For example, an unrecognized
jvm option is used. Please refer to the user guide chapter on the
daemon at http://gradle.org/docs/2.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
Unrecognized VM option 'MaxPermSize=256m' Error: Could not create the
Java Virtual Machine. Error: A fatal exception has occurred. Program
will exit.
I read this and tried all the ways to solve it but to no avail. I did notice that his error was somewhat different from mine and thought that might be why I couldn't solve my problem using the ways suggested.
As I executed the .sh file on my terminal, it printed:
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=250m;
support was removed in 8.0
(java:5094): Gtk-WARNING **: Unable to locate theme engine in
module_path: "pixmap"
Gtk-Message: Failed to load module "canberra-gtk-module"
I'm not sure whether it's related to the error or not. Please help.

In my case I had a line
org.gradle.jvmargs=-Xmx6408m -XX:MaxPermSize=6408m -XX:+HeapDumpOnOutOfMemoryError
in my gradle.properties file in the project structure.
removing -XX:MaxPermSize=6408m from that file fixed an issue

As it was already said in this thread, Permanent Generation was removed in Java 8, which is used in your case. I think, the easiest solution is to remove parameters associated with Permanent Generation during program execution.
Go to the directory where you have Android Studio. Then go to the bin/ subdirectory. Locate the following files, which contains Java Virtual Machine options:
studio.vmoptions
studio64.vmoptions
Open these files and locate line with MaxPerSize parameter. It should look as follows:
XX:MaxPermSize=256m
Remove this line in both files. I don't know if you are using 32-bit or 64-bit operating system, so you can update both files just in case.
I'm not sure if it will solve your problem, but I would try it in such situation. In my case, with this option and Java 8, I just get the warning, but Android Studio starts anyway. After removing this parameter, Android Studio still starts, but without warning. I'm using Ubuntu 14.04 LTS.
EDIT:
There is another solution for this problem described here: https://stackoverflow.com/a/27913562/1150795.
Go to File > Other Settings > Default Project Structure > JDK location and check the path.
In case of Ubuntu Linux, we can set /usr/lib/jvm/java-7-oracle as default JDK if we are using Oracle JVM. JDK 7 is the safest option for Android.

-XX:MaxPermSize was deprecated in JDK 8, marked as obsolete in JDK 16, and removed in JDK 17. It was superseded by the -XX:MaxMetaspaceSize option.
Change -XX:MaxPermSize to -XX:MaxMetaspaceSize solve my problem.
ref:
https://github.com/expo/expo-cli/issues/4196#issuecomment-1035850918
https://docs.oracle.com/en/java/javase/17/docs/specs/man/java.html#removed-java-options

In my case opening $ANDROID_HOME/tools/lib/monitor-x86_64/monitor.ini and removing
XX:MaxPermSize=256m
from it did the job.

Oh I've solved this problem, I install Oracle JDK 9 when android studio runs on JDK 6 or JDK 7 (if I'm not mistaken).
so I uninstalled Oracle JDK 9, then download and install the JDK 7.

On MacOS the following clause in ./gradlew injects this option:
# For Darwin, add options to specify how the application appears in the dock
if $darwin; then
GRADLE_OPTS="$GRADLE_OPTS \"-Xdock:name=$APP_NAME\" \"-Xdock:icon=$APP_HOME/media/gradle.icns\" \"-Xmx1024m\" \"-Xms256m\" \"-XX:MaxPermSize=1024m\""
fi
This file can be edited by hand after the project has been generated.

i had the same issue and i was able to solve it by adding this directly in the terminal
export JAVA_VERSION=1.8
and then try the

JetBrains IntelliJ Error launching Intellij Platform - Error invoking main method

I have IntelliJ IDEA and other JetBrains products installed and they worked great (PyCharm, Android Studio, Clion, WebStorm) till today, now I just get opening message:
Error launching Intellij Platform - Error invoking main method
I have installed:
C:\Program Files\Java\jdk1.8.0_25
C:\Program Files\Java\jre1.8.0_25
and JAVA_HOME is pointing to jdk.
I posted at: https://devnet.jetbrains.com/message/5533036#5533036 and https://devnet.jetbrains.com/thread/459951
I installed (clean) Windows 8.1 and now it works, but there should be option to wipe all java configs from Windows to avoid such mess, cause this is not the solution.

I meet this error today. Java update message jump out when I work with AndroidStudio. I accept it but my AS can't display res files after installation. I restart AS and see the error.
I guess new version java produce the error. The updated java part is jre, version is 1.8.0_101, but jdk's version is still 1.8.0_92. So I download and install new version jdk(1.8.0_101, the same as jre).
AndroidStudio successfully starts now.
Maybe this solution can also work to IDEA.

For people who couldn't solve it by having the same version of JDK and JRE.
Uninstall IntelliJ and also clean all the files that are not swept automatically by uninstalling. you can find them in C:\Users\Usuario\AppData on Local and LocalLow find the JetBrains folder and delete all the files related to IntelliJ.
Then proceed to reinstalling it. That solved it for me.

Eclipse SVN Synchronze workspace error - Updating Synchronize view for SVN Workspace - java/nio/file/Paths

I updated the Eclipse SVN plugins today and after that I can't sync my workspace with SVN repository.
I am using java 1.6. I tried with java 1.7 as well. still I'm getting following error in eclipse.
An internal error occurred during: "Updating Synchronize view for SVN Workspace.".
java/nio/file/Paths.
SVN: '0x00000025: Send Notifications' operation finished with error:
java/nio/file/Paths
This issue came only after updating the svn plugin. I'm using SVNKit 1.7.13 svn connector.
Any idea how to solve this??
Thanks

Found a work around for this.
Uninstalled all svn plugins from Eclipse and restarted it.
Installed Subclipse svn plugin from http://subclipse.tigris.org/update_1.10.x

I had the same error when I opened Eclipse. Checking the file: workspase-path/.metadata/.log I found the following exception:
!MESSAGE SVN: 'SVN Decorator' operation finished with error: java/nio/file/Paths
!STACK 0
java.lang.NoClassDefFoundError: java/nio/file/Paths
at org.eclipse.team.svn.core.utility.SVNUtility.getNodeKind(SVNUtility.java:1145)
...
To solve the problem I installed JRE 1.7, then I changed eclipse.ini to force Eclipse to use it, adding the next at the beginning:
-jv
"path-to-jre7/bin/javaw.exe"

I had the same problem in Luna on Win 7 64 bit with the 2.0.3 subversive team provider and the Polarion SVNKit 1.8.7 version 4.1.2. Clearly somewhere in these java 7 is needed. Servaq's suggestion improved things for me but didn't quite fix everything. But a similar change to eclipse.ini did the trick for me: I added
-vm
C:\Program Files\Java\jre7\bin\server\jvm.dll
right before the -vmargs. Obviously, the path to server\jvm.dll is installation-dependent.
Just in case it's helpful to Chandika ("I wants to use java 1.6"),
I'm still using java 6 as the compiler/runtime for the code I'm developing within this eclipse. I'm just using java 7 to start eclipse.