Frequently Asked Questions

Frequently Asked Questions

• What do I do when NiCE throws up a box that says "Uncaught exception thrown in ThreadLWJGL Renderer Thread,6,main java.lang.UnsatisfiedLinkError: org.lwjgl.opengl.LinuxMouse.nGetButtonCount(J)I?"
• Why can't NiCE find mpirun on a remote machine?
• Why can't NiCE find the hdf-java libraries?
• Should I put spaces in file paths with NiCE?
• What are the weird file names in NiCE's Windows INI file?

What do I do when NiCE throws up a box that says "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 a NiCE developer and can't find a .jme3 directory, the files may exist in a locally installed version of IBM Rational Software Architect, (/home/yourUser/IBM/SDP on Linux). Delete all of the lib*.so files from this directory except for libcairo-swt.so.

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

Sometimes executing a remote job from NiCE will fail with a message like "bash: mpirun: command not found...". This normally happens because the directory in which MPI is installed is not on the path on the remote machine or was improperly added to the path (misspelled word or something).

If you know for a fact that the MPI installation is on the path, make sure it is added to the path for interactive, non-login shells. NiCE 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 (or other appropriate file if you use a different shell).

Why can't NiCE find the hdf-java libraries?

See Getting NiCE for more information on how to properly configure your hdf-java libraries on Linux and Windows. If configuring your PATH does not work as shown there, you can always set -Djava.library.path in the NiCE.ini configuration file. We only recommend this as a last resort.

Should I put spaces in file paths with NiCE?

Windows: Yes
Linux & Mac: Yes, so long as they are preceded by the escape character "\" as in "My\ Folder\ With\ Spaces."

What are the weird file names in NiCE's Windows INI file?

Do you mean something like these guys?

-Dvisit.binpath=C:\PROGRA~1\LLNL\VISIT2~1.2
-Djava.library.path=C:\PROGRA~1\THEHDF~1\HDFVIE~1.9\lib\win

These are the paths to VisIt and HDFView written with Windows 16-bit file names also known as "short names." This is an alternative way to specify file paths in Windows and NiCE 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. This could be, for example:

-Dvisit.binpath=C:\Program Files\LLNL\VisIt 2.5.2
-Djava.library.path=C:\Program Files\TheHDFGroup\HDFView2.9\lib\win

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