Name: gm110360 Date: 11/30/2001
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)
There is currently no way for distinguish between severe io exceptions and
exceptions raised due to a full disk.
If a write operation failed the state of the file is unknown (is some or no
data written, can be read from the file?)
In detail: I implented a tempfile class which deletes the file in finalize().
Due to the garbage collection it may take a very long time until an old
tempfile object is removed and therefore the file lays for several hours
unnecessary on the disk and blocking disk space.
In case of a disk full exception the tempfile class may call the garbage
collector to force getting rid of unreferenced tempfiles.
(Review ID: 136520)