Page 1 of 1

seadas-7.4 GUI java exception

Posted: Sun Mar 12, 2017 11:37 am America/New_York
by obdaac_forum_user
I have installed the latest version of seadas-7.4 on a linux 64bit Centos 7.3.1611 server running an X-windows client (X2GO). The previous 7.3 version of the GUI worked reasonably well, but after installing 7.4, there is no response after entering the seadas command and the contents of the stderror.log file in $HOME/seadas-7.4/bin are the following:

$ cat seadas-7.4/bin/stderror.log
Error: null
java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  at com.bc.ceres.launcher.Launcher.launch(Launcher.java:151)
  at com.bc.ceres.launcher.Launcher.main(Launcher.java:56)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:65)
  at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:57)
Caused by: java.awt.HeadlessException
  at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)
  at java.awt.Window.init(Window.java:484)
  at java.awt.Window.<init>(Window.java:436)
  at java.awt.Window.<init>(Window.java:561)
  at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor$CeresSplash.<init>(SplashScreenProgressMonitor.java:423)
  at com.bc.ceres.core.runtime.internal.SplashScreenProgressMonitor.createProgressMonitor(SplashScreenProgressMonitor.java:93)
  at com.bc.ceres.core.runtime.RuntimeFactory.createProgressMonitor(RuntimeFactory.java:95)
  at com.bc.ceres.core.runtime.RuntimeFactory.createRuntime(RuntimeFactory.java:66)
  at com.bc.ceres.core.runtime.RuntimeLauncher.launch(RuntimeLauncher.java:41)
  ... 12 more

I also checked which Java version is running and found the following:

$ java -version
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

Any suggestions?
Thanks.

seadas-7.4 GUI java exception

Posted: Sun Mar 12, 2017 1:20 pm America/New_York
by gnwiii
The log shows "Caused by: java.awt.HeadlessException".  In plain language, this says Java didn't find keyboard, mouse, or display so is running in "headless" mode.

seadas-7.4 GUI java exception

Posted: Mon Mar 13, 2017 8:22 am America/New_York
by OB.DAAC - SeanBailey
Yes, the SeaDAS needs to be launched from a shell with a display.  If you launched from a terminal in X2Go, I *think* all you would need to do is make sure the DISPLAY variable is set to whatever X2Go is using.

Sean

seadas-7.4 GUI java exception

Posted: Mon Mar 13, 2017 3:03 pm America/New_York
by obdaac_forum_user
We have tried various settings for the DISPLAY environment variable and none seem to work. Folks here seem to think the problem resides with the Java interface. We have also tried different XWindows clients and even connected directly to the server and have not been able to get past the error. Other X applications seem to be working fine.

???

seadas-7.4 GUI java exception

Posted: Mon Mar 13, 2017 3:26 pm America/New_York
by OB SeaDAS - dshea
I noticed that you are running OpenJDK.  We have lots of display problems with OpenJDK, so I would suggest installing Oracle JDK and see if that solves the problem.  I know the performance will be much better.

don

seadas-7.4 GUI java exception

Posted: Mon Mar 13, 2017 3:28 pm America/New_York
by obdaac_forum_user
I was able to  resolve this by reinstalling java-openjdk. Working now!
Thanks.

seadas-7.4 GUI java exception

Posted: Mon Mar 13, 2017 11:22 pm America/New_York
by OB SeaDAS - dshea
I would really suggest using Oracle JDK. The graphics artifacts and drawing performance are quite hindering with Open JDK

don