DataStax DevCenter stuck on Startup

Question

I just installed DataStax DevCenter. However when loading up, the Automatic Update & Usage page pops up. However the "Ok" button is disabled and unclickable. So I can't get pass the startup loading of the application. How can I bypass this?

Click here for screenshot

Weever

Answer 1

This sounds very much like a known issue with DevCenter and Java versions 1.8.0_152 or Java 9.

Are you using either of those? Use java -version on the command line to quickly check which version is being used.

The only workaround at this time is to use a different version of Java - version 1.8.0_151 or earlier should be fine.

Adagio

Answer 2

You can have multiple JDKs and configure DevCenter to use earlier one.

Right-click on DevCenter.app in your properties directory Click “Show package contents” Open Contents/info.plist in an editor of your choice Then, at the bottom you will find configuration that looks like the following:

<dict>
    <!-- a lot of stuff above -->
    <key>Eclipse</key>
    <array>
        <!-- comments on how to change the Java version -->
        <string>-keyring</string><string>~/.eclipse_keyring</string>
        <string>-showlocation</string>
        <!-- some more comments -->
    </array>
</dict>

Into the array element, insert the following children and make sure to adapt the old Java version you want DevCenter to use and your users name.

<string>-vm</string>/Library/Java/JavaVirtualMachines/1.8.141.jdk/Contents/Home/bin/java</string>

Depreciatory

Note, if you did brew install adoptopenjdk8, you would now add the line <string>-vm</string><string>/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/java</string> – Ruskin

Opening tag for string in jdk path is missing in the answer. e.g. <string>-vm</string><string>/Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/bin/java</string> – Canned

Answer 3

For me just changing the JAVA_HOME point to 1.8.0_151 did not work. Only after completely removing all other Java versions from machine, fixed the issue for me. Hope it helps

Expel

Answer 4

Changing to Java version _131 worked for me.

Weever