In the last couple of weeks, I get more and more reports of problems running JDeveloper 12.2.1.x. (to be exact 184.108.40.206.0, 220.127.116.11.0 and 18.104.22.168.0)
The problems reported are
- properties editor not working
- JDeveloper hangs during start
- showing wireframe instead of page design
- problems to configure the JDBC connection
- problems compiling expression on attributes (not 100% verified that this is JDK problem)
- problems migrating projects created with earlier versions of JDeveloper
- problems with the groovy script engine
- deadlocks within JDeveloper when editing multiple java files
to name some. The problems are not ADF related but IDE related. It turned out that they only could be reproduced if the used JDK to run JDeveloper on was newer than JDK 1.8.0_101. All problems are not reproducible when running JDeveloper with JDK 1.8.0_101.
Currently, there is a bug pending (Bug 26766333) with support.oracle.com for some but not all mentioned issues. At the moment of writing this, there is no patch available.
My recommendation is to install JDK 1.8.0_101 and run JDeveloper using this JDK. You can do this by
- installing JDK 1.8.0_101 on your machine. The download for this old version is hard to find in the WWW. To make it easier, you can find it on this page: Java SE 8 Archive Downloads
- change the product.conf file you’ll find in your .jdeveloper folder inside your home folder. Open the file and set the SetJavaHome property
- to be on the safe side, you can recreate the integrated WLS to make it use JDK 1.8.0_101 too. If you know our way in the jungle of script files which are used to start the embedded WLS, you can change those files directly. As there typically are not many changes made on the integrated WLS, I find it easier to delete the integrated WLS and create it again. It’ll pick up the JDK JDeveloper is running on automatically and use it to run the WLS too.
You don’t need to update or change the JDK your standalone server is running on. To my knowledge, the problems are only IDE related, so they don’t affect the running application.
If you find a problem, which is related to using a JDK newer than 1.8.0_101, feel free to leave a comment on this post. I’ll add them to the list for reference.