]
Ondrej Dockal updated JBDS-4756:
--------------------------------
Sprint: devex #164 April 2019 (was: devex #163 March 2019)
Cannot start devstudio on mac os with jdk 11
--------------------------------------------
Key: JBDS-4756
URL:
https://issues.jboss.org/browse/JBDS-4756
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Bug
Components: installer
Affects Versions: 12.11.0.AM1
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Priority: Critical
Fix For: 12.11.0.GA
Attachments: Screenshot_20190204_115602.png
I can easily install devstudio on mac os with default jdk 11 (from
/qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings
except the one here:
!Screenshot_20190204_115602.png|thumbnail!
More info links [
here|https://support.apple.com/kb/DL1572?locale=en_US].
I can also see installer
[
tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...]
failures on mac os 10.12 and 10.13 with this tack trace:
{code}
java.awt.HeadlessException
at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186)
at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244)
at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237)
at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at com.sun.proxy.$Proxy0.invoke(Unknown Source)
at
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
{code}
It might be possible to at least to try the installation and run on some bare metal to
verify this error. Could someone possibly assist here, please? I have a suspicion that it
might be performance related as the time needed to even open the jdk folder on the shared
drive takes quite some time. Thanks!