After double-clicking on the SimulationContainer.bat file a window appears and then disappears.

Open a cmd window and run the SimulationContainer.bat file from the command line. Based on the error shown, follow one of the solutions below.

'java' is not recognized as an internal or external command, operable program or batch file.

The J2SE 1.4 JRE is not in the system path. Edit the SimulationContainer.bat file and add the path to the JRE.

java.lang.UnsupportedClassVersionError: com/realityinteractive/jsc/container/standalone/ContainerStart (Unsupported major.minor version 48.0)

A 1.4.X JRE is required to use the Simulation Container. Get and download a J2SE 1.4.2 SDK. Edit the SimulationContainer.bat file and add the path to the 1.4.X JRE if necessary.

The start button is grey-out and cannot be pressed.

There is no simulation loaded in the container. After loading a simulation all buttons on the toolbar will be available.

The start button does not stay pressed in and the simulation does not run.

There was an error while deploying the simulation. Look in the cmd window associated with the Simulation Container. Based on the error shown, follow one of the solutions below.

A ClassNotFoundException was thrown.

ClassNotFoundException may be thrown for many reasons:

• A class file has not been compiled. Check the classes directory and ensure that the file exists. If not the class may not have been successfully compiled.
• A required JAR is not in the lib directory. Some simulations require that other JARs are downloaded and placed into the lib directory. For the tutorials, ensure that the Simulation Common jar is in the classpath of the Simulation Container.
• The simulation deployment descriptor is not correct. It is common to misspell a classname in the deployment descriptor.

After refreshing a simulation, the simulation can no longer be started.

Typically, the same problems that can prevent a simulation from being loaded will prevent a simulation from being successfully refreshed. In addition to the Staring a Simulation questions above the following may have occurred:

• Stages may have objects that are controlled by other stages. When the controlling stage is refreshed it is possible that the shared objects are no longer valid. The simulation should be redeployed.

All classes are being reloaded when the simulation is refreshed.

The Simulation Container uses the modification time on the classes to know which are to be reloaded. Make sure that an incremental compiler such as Jikes is used. This will ensure that only those java files that have been modified are the ones that are recompiled which in turn will be the ones that are reloaded.