ICE FAQ

This page is designed to address some general questions and issues ICE users have. We also have a MOOSE FAQ for MOOSE-specific questions.

What do I do when ICE throws up a box that says something about an uncaught exception in the LWJGL Renderer?

Error message: Uncaught exception thrown in Thread[LWJGL Renderer Thread,6,main] java.lang.UnsatisfiedLinkError: org.lwjgl.opengl.LinuxMouse.nGetButtonCount(J)I

This error happens because jMonkeyEngine 3 (jME3) is unable to find the proper version of the LWJGL library on your system. Members of our development team have been able to fix it by removing the .jme3 directory from their home directories.

If you are an ICE developer and can't find a .jme3 directory, the files may exist in a locally installed version of IBM Rational Software Architect (/home/<user>/IBM/SDP on Linux). Delete all of the lib*.so files from this directory except for libcairo-swt.so.

Why can't ICE find mpirun on a remote machine?

Sometimes executing a remote job from ICE will fail with a message like "bash: mpirun: command not found...". This normally happens because the directory in which MPI is installed is not included in the remote machine's $PATH variable, or was improperly added to the system's $PATH (like a misspelled word, for example).

If you know for a fact that the MPI installation is on the $PATH, make sure it is added for interactive, non-login shells. ICE does not create a login shell when it launches remote jobs, it only creates interactive shells that can take and execute a single command. The simplest way to fix this is to add the information about the MPI path to your ~/.bashrc configuration (or other appropriate file if you use a different shell).

Should I put spaces in filepaths with ICE?

Windows: Yes Linux & Mac: Yes, so long as each space is preceded by the escape character, '\' (as in "Some\ Pathname\ With\ Spaces.")

What are the weird filepaths in the ICE.ini file? (Windows only)

Do you mean something like these guys?

-Dvisit.binpath=C:\PROGRA~1\LLNL\VISIT2~1.2
-Djava.library.path=C:\PROGRA~1\HDF_Group\HDFView\2.10.1\lib

These are the paths to VisIt and HDF-Java libraries, written with Windows 16-bit file names also known as "short names." This is an alternative way to specify file paths in Windows, and ICE uses it to get around a bug in the Eclipse Platform's Product Configuration File Generator. Eclipse Products can not handle spaces in filenames or other special characters at build time, but you are free to change it to a more readable format at deployment time. You could change it to full filepaths, for example:

-Dvisit.binpath=C:\Program Files\LLNL\VisIt 2.8.2
-Djava.library.path=C:\Program Files\HDF_Group\HDFView\2.10.1\lib

Windows will convert these to the short forms under the hood.