Reputation: 774
The newly created daemon process has a different context than expected.
It won't be possible to reconnect to this daemon. Context mismatch:
Java home is different.
Wanted:DefaultDaemonContext[uid=null,javaHome=/home/administrator/Downloads/idea-IU-145.1617.8/jre,daemonRegistryDir=/home/administrator/.gradle/daemon,pid=11963,idleTimeout=null,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]
Actual:
DefaultDaemonContext[uid=4839fb8c-418b-4666-9a66-40a60133958a,javaHome=/usr/lib/jvm/java-8-openjdk-amd64,daemonRegistryDir=/home/administrator/.gradle/daemon,pid=15202,idleTimeout=60000,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]
Upvotes: 47
Views: 34105
Reputation: 831
Java home is different.
Expecting: '/Users/******/.sdkman/candidates/java/current' but was: '/Users/*****/.sdkman/candidates/java/11.0.16.1-zulu/zulu-11.jdk/Contents/Home'.
Please configure the JDK to match the expected one.
for me me none of any of those suggestion worked. I am using mac with sdk man to manage the jdks. I checked gradle wrapper version in gradle/wrapper/gradle-wrapper.properties
and updated from 6.8.2
to 6.9.3
and it worked.
Upvotes: 0
Reputation: 6033
I struggled it whole day. For my case, it's not related to intellij. But as the repo uses an very outdated version of gradlew of 4.9. And it always complain a about a particular pid
in the same error message. Which when I using jps
or ps
, it wasn't there. That drives me crazy. I reboot my machine many times, it still complains about the same pid. Later I found it cached the pid in the folder of: ~/.gradle/daemon/...
. Such a dumb error message and logic. The finally I solved this problem but cleanup the whole ~/.gradle
folder.
Upvotes: 0
Reputation: 41
Worked like magic.. have been struggling for 2 days now, just add:
org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home
in ~/.gradle/gradle.properties
file.
Upvotes: 3
Reputation: 3978
For me this is solved when I selected the Project SDK
option in gradle JVM. Even it was same when selected manually.
the preference window in intellij
Upvotes: 2
Reputation: 1301
The mentioned methods did not work for me. I am using Big Sur 11.4, M1 mac.
Remove Java like in the link below and reinstall it: https://actonnotes.wordpress.com/2020/11/22/how-to-remove-openjdk-version-15-on-apple-macos/
Upvotes: 0
Reputation: 186
IntelliJ broke when I copied tools.jar
to a jre/lib
, attempting to make hot attach work.
Upvotes: 3
Reputation: 1138
Be sure to check and correct JDK version in these 3 places:
Preferences -> Build,... -> Build Tools -> Gradle -> Gradle JVM
:
Project Structure -> Project Settings -> Project -> Project SDK
:Project Structure -> Platform Settings -> SDKs
:
Fixing gradle.properties is a dirty workaround. Better fix this at the IDE level.
Upvotes: 70
Reputation: 1617
Fwiw - Had a similar thing after, and just reopening the project by picking the build.gradle file fixed it. (Also, done brew cask install java
which placed jdk 10 in the default path)
Upvotes: 1
Reputation: 4023
I ran into the same problem. This answer helped me.
Solution: In the bin folder of IntelliJ where you have it installed, run idea64.exe
not idea.exe
.
Upvotes: 1
Reputation: 558
Though I did not find the root cause where the different javaHomes have been taken from, at least I found a workaround that worked for me:
Try setting the following in your gradle.properties
(either in $HOME/.gradle/
or in your project build dir):
org.gradle.java.home=/usr/lib/jvm/java-8-openjdk-amd64
Upvotes: 44