Home News People Projects Publications Technical Pages
   
Object Network toolkit
Overview
Screenshots
Download
Installation
Getting Started
Documentation
Bug Report
Troubleshooting
Known Bugs and Reported Errors
Revision History
 
 

Troubleshooting

As a first advice, I'll assume your path points to the binary directory from the installation tree of the Java Development Kit.

P: I typed 'java install' in the same directory I put the file install.class but it reported 'Exception in thread "main" java.lang.NoClassDefFoundError: install'.
A: Just a non default option. Try 'java -classpath . install'.

P: The installation wizard seems to work fine, but when I press 'Close' button on the Install Wizard the window closes normally but it freezes and does not quit to the console where it was started.
A: take a look at here.

P: When I try to start any program under Solaris 2.6 it crashes and reports 'Segmentation Fault'.
S: This is possibly due to a missing Solaris 2.6 patch-fix needed by the production release of the JDK1.2.X. Download the required patch and apply it to the operating system.

P: When I try to start the graphical user interface it raises 'Exception in thread "main" java.lang.NoClassDefFoundError: javax/swing/JFrame' or something like that.
S: Type 'java -version' to see whether you're using the final version of JDK (1.2.X). Remember that there are several naming conventions for JFC packages that have changed since the beta release. You do need the final release to run this system. Look at the requirements list.

P: I was working on the graphical user interface and suddenly it closed, dumping the stack trace. What should I do?
S: Check the stack trace for the exception message and the console server logs and send us a report bug describing the context in which the error occurred.

P: The simulation window seems frozen at the beginning of the simulation.
S: Check your TCP/IP configurations for DNS. If your computer has some DNS server specified this machine should be reachable from your system, otherwise the resolver library will time-out every time. As a last resort you can disable any DNS searching. This problem is not a bug, it's just a consequence derived from the way DNS works. The release 1.1_3 tries to avoid name lookups.
 
 
 

 

Send a mail to our webmaster for any questions or comments about this web site.

Copyright © 1999 Computational Semiotics Group

Last modified: 23th May, 2000 .