Installation Troubleshooting

I do not have the Java version required to run Iris.

When you run the Iris startup command, the application does not open; the SED Importer startup command fails with an error message.

% /path/iris-1.0-<plat>-<arch>/Iris &

[nothing happens]


% /path/iris-1.0-<plat>-<arch>/SedImporter &

 Exception in thread "main" java.lang.ClassFormatError: cfa.vo.sed.importer.SedImporterApp (unrecognized class file version)
   at java.lang.VMClassLoader.defineClass(libgcj.so.7rh)
   at java.lang.ClassLoader.defineClass(libgcj.so.7rh)
   at java.security.SecureClassLoader.defineClass(libgcj.so.7rh)
   at java.net.URLClassLoader.findClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
   at gnu.java.lang.MainThread.run(libgcj.so.7rh)

This likely indicates that you do not have the minimum required Java version on your system to run the Iris application; or you do, but your global 'path' variable points to an older Java version which coexists on your system with the up-to-date one. In the case of the former, you should upgrade to at least Java SE 6 (version 1.6) by following the installation instructions for the Java Runtime Environment (JRE) specific to your computer platform, on the Oracle website.

In the case of the latter, first check to see if your path points to an older version of Java on your system; if so, contact your systems administrator to find out if a newer version of Java is available elsewhere on your system.

For example, the output below shows that the global path variable is pointed to a directory containing an outdated version of Java.

% which java
/usr/bin/java

% java -version
java version "1.4.2"
gij (GNU libgcj) version 4.1.2 20080704 (Red Hat 4.1.2-50)

Checking /usr/local/bin, however, reveals that an up-to-date Java version coexists on the system with the older version:

% /usr/local/bin/java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)

Editing the global path variable so that the directory containing Java SE 6 is searched before the directory containing the older version, will allow Iris to properly install.

% set path = (/usr/local/bin $path)

% Iris &

Adding the "set path ..." line shown above to your user preferences file for the shell, e.g. ~/.cshrc.user or ~/.cshrc for the tcsh shell or ~/.bashrc for bash shell, will make this change permanent; running it in the terminal window will alter the path only temporarily, i.e., for that particular terminal session.

The Iris Fit feature does not appear to be working.

If you find that the components of Iris, Specview and Sherpa, are not communicating (via SAMP) as they should - e.g., when you try to fit a model to a data set within Iris using the Fit feature, nothing happens - then it is likely that Specview was not able to initiate a SAMP hub with which to connect to Sherpa. To see if this is the case, check the SAMPSherpa.log in the Iris installation directory for error messages, as well as the report from the Iris installation smoke test.

This is a known bug with the software which is often not reproducible. On some Linux Fedora systems, using JRE from Oracle in place of OpenJDK which comes on these systems may resolve the issue. Removing the SAMP lockfile in your home directory may also resolve the connection error.

% rm ~/.samp

If these actions do not not help, it is possible that a spurious Sherpa process may be running and need to be ended; see the next section for details.

If you encounter this error and need assistance, please contact the VAO Helpdesk.

I exited Iris with a Force Quit or 'kill' command; now it does not run properly.

If the Iris application is killed off either by Force Quit (on Linux or Mac) or the 'kill' command, as opposed to the Iris "File -> Exit" menu option, the Sherpa program may survive as a spurious Python process. As a result, the next time you try to use Iris, it may not work properly. To remedy the problem, you can end the spurious process using 'ps' and 'kill' or using System Monitor. The process name should appear as something like 'python2.6'.

This occurs because Iris is responsible for starting and stopping the Sherpa Python process. If Iris is killed without executing its usual shutdown procedure, Sherpa could be left running. Since Iris uses SAMP to communicate, the spurious Sherpa process can conflict with Iris when it tries to establish a new connection.

You can also confirm the issue by inspecting the Iris log file located in your Iris download directory, which may appear as follows:

% more <basedir>/iris-1.0-<plat>-<arch>/lib/spv/iris.log

Sep 22, 2011 10:38:28 AM
org.astrogrid.samp.client.HubConnector$ConnectorCallableClient
receiveResponse
WARNING: Response handler failed
java.lang.ArrayIndexOutOfBoundsException: 911
        at spv.util.YUnits.convert(Unknown Source)
        at spv.glue.PlottableFittedSpectrum.updateDataSets(Unknown Source)
        at spv.view.AbstractPlotWidget.buildDataSetList(Unknown Source)
        at spv.view.BasicPlotWidget.buildAndAttachDataSets(Unknown Source)
        at spv.view.BasicPlotWidget.assembleCanvases(Unknown Source)
        at spv.view.FittingPlotWidget.assembleCanvases(Unknown Source)
        at spv.view.AbstractPlotWidget.plot(Unknown Source)
        at spv.view.AbstractPlotWidget.doPlot(Unknown Source)
        at spv.view.AbstractPlotWidget.dataUpdated(Unknown Source)
        at spv.view.AbstractPlotWidget.update(Unknown Source)
        at java.util.Observable.notifyObservers(Observable.java:159)
        at spv.spectrum.SpectrumDecorator.update(Unknown Source)
        at java.util.Observable.notifyObservers(Observable.java:159)
        at spv.fit.FittedSpectrum.update(Unknown Source)
        at java.util.Observable.notifyObservers(Observable.java:159)
        at spv.spectrum.ContinuousIntensity.computeValues(Unknown Source)
        at spv.spectrum.ContinuousIntensity.update(Unknown Source)
        at spv.fit.SEDFittedSpectrum.setModelValues(Unknown Source)
        at spv.controller.SherpaModelManager.handleModelValues(Unknown
Source)
        at spv.controller.SherpaModelManager.access$400(Unknown Source)
        at
spv.controller.SherpaModelManager$SpectrumFitCalcModelValuesHandler.result(Unknown
Source)
        at
org.astrogrid.samp.client.HubConnector$CallItem.processResponse(HubConnector.java:1172)
        at
org.astrogrid.samp.client.HubConnector$CallItem.addResponse(HubConnector.java:1129)
        at
org.astrogrid.samp.client.HubConnector$CallHandler.receiveResponse(HubConnector.java:1046)
        at
org.astrogrid.samp.client.HubConnector$ConnectorCallableClient.receiveResponse(HubConnector.java:892)
        at
org.astrogrid.samp.xmlrpc.ClientXmlRpcHandler$ClientActorImpl$3.run(ClientXmlRpcHandler.java:133)

Error: spv.view.ViewException: spv.graphics.GraphicsException: Graphics:
Error in buildind Data Set.