We got a complaint on the Gitter that inspectIT UI is again problematic on Mac after an update to OSX High Sierra.
When I launch from command line like above it is still frozen. No difference.
Using JDK 1.8.0_152-b16.
I do have a similar problem, but starting with
neither JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home /Applications/inspectit/inspectIT.app/Contents/MacOS/inspectIT -debug
nor /Applications/inspectit/inspectIT.app/Contents/MacOS/inspectIT -debug -vm /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home
The first one as well as not setting the environment variable ends with the try to find a new version and a frozen UI with the following modal dialogue window:
The debug output is
(Looks like the JAVA_HOME is not respected by the launcher? However the /Library/Java/JavaVirtualMachines/CurrentJDK is only a SymLink to /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk.
The second approach shows the following output:
and a dialogue asking to install a JRE.
As many people are hitting the same problem, we will try to address this soon. At least in order to find a workaround.
Any chance you can spare some time to help me out here? If yes, please contact me
Tested on Mac OSX 10.13.3 (17D47). Everything works fine, the UI starts and it's not frozen. The application uses the VM in JDK 1.8.131.
Here is the successful debug log output part:
I see that people complaining are using JDK 1.8.152 or even java 9. I am not sure if this has any effect. It would be great if somebody can install the JDK 1.8.131 version and try with that, at least we would confirm that the VM is the problem. The command should be then:
In other operating systems we have no problems with newer 1.8 JVMs. Java9 could be a problem and should be avoided.
As part of this ticket, I will update the run.sh file, as it's missing the shebang line and execution mod.