I have a type of number crunching program, and as I wanted to be able to interrupt it and continue it later, I put everything in a single control class and several depending classes. At interrupt time, I write the control class (and implicitely the depending classes) with Java Object IO, at restart time, I read it again.
This works fine for the first time - or for the first two or three interrupts. But as the runs are longer (or, perhaps, my class has more subclasses), I just get an IO error that I do not understand. It occurs when I write the control class; my call to writeObject comes (via other classes) to a java.io.IOException: write error.
The problem seems to be reproducable (however, after two runs of about 5 hours, each, on a 300 MHz Windows computer).
Did anybody hear about a similar problem with serialization? Or is it more likely that it is a problem of the system, that was heavily loaded for CPU and virtual memory?
Thanks in advance
This works fine for the first time - or for the first two or three interrupts. But as the runs are longer (or, perhaps, my class has more subclasses), I just get an IO error that I do not understand. It occurs when I write the control class; my call to writeObject comes (via other classes) to a java.io.IOException: write error.
The problem seems to be reproducable (however, after two runs of about 5 hours, each, on a 300 MHz Windows computer).
Did anybody hear about a similar problem with serialization? Or is it more likely that it is a problem of the system, that was heavily loaded for CPU and virtual memory?
Thanks in advance
