In Oct 2000, Debrief was modified in order that errors and stack traces were written to a log file suitable for transmission back to MWC. The trace file is named "trace.txt" and is created afresh each time Debrief is run (and a trace is required). The file is normally placed in the directory from which the application was started. The format/content of the file is as follows:
Table 12-2. Debrief Error Traces
Content |
Description |
|---|---|
|
Stack trace started at:Mon Oct 09 13:44:17 GMT+01:00 2000 |
Header Information |
-- listing properties --
java.runtime.name=Java(TM) 2 Runtime Environment, Stand...
sun.boot.library.path=C:\Program Files\JavaSoft\JRE\1.3\bin
java.vm.version=1.3.0-C
java.vm.vendor=Sun Microsystems Inc.
... ETC, ETC, ETC
java.ext.dirs=C:\Program Files\JavaSoft\JRE\1.3\lib...
sun.boot.class.path=C:\Program Files\JavaSoft\JRE\1.3\lib...
java.vendor=Sun Microsystems Inc.
file.separator=\
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport...
sun.cpu.endian=little
sun.io.unicode.encoding=UnicodeLittle
user.region=GB
sun.cpu.isalist=pentium_pro+mmx pentium_pro pentium+m...
****************------------- |
Settings for this PC / Java installation |
****************-------------
java.io.StreamCorruptedException: InputStream does not contain a serialized object
at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.<init>(Unknown Source)
ETC, ETC, ETC
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
|
Stack trace for errors as they occur |
This error trace may be examined for hints to the problem occurring. The error trace may be viewed in a text editor, and may be forwarded back to the Project Manager via post/e-mail/fax as applicable. The file does not contain any details of the data being edited, but the file should still be inspected before transmission
If these error messages do not provide any insight to the problem, you are left with the normal diagnosis steps as follows:
Try to run another Java application on the machine, to check that Java is not corrupted
If Java is ok then,
Check that Debrief can open and process the "sample" files included in the installation: boat1.rep and boat2.rep.
If Debrief can process these files, but not the current ones then
Try to re-install the Debrief application from 'save' disks to check that the sources are not corrupted
If at this point the error is still occurring then you will have to resort to reading as much of this Help guidance as practical, and then contacting the Project Manager