On Dec 30, 2007, at 7:39 PM, Adrian Bartholomew wrote:
Would handling it wont solve it? Wouldnt the problem still exist?
It never happened before though i can't trace what I did, when.
Also, what does that particular exception indicate?
Google java.io.EOFException. That indicates that some i/o throws this
to indicate EOF instead of returning -1 or some other 'special
value'. So handling it might be a complete fix. However, it looks
like you're doing RMI or something else based off of serialization
and I don't remember ever running into this exception with either of
those.
So you may have an actual problem involving incomplete serialized
object input streams. But the problem then is most likely on the
sending end, sending early or sending truncated?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
References:
>EOF Exception (From: Adrian Bartholomew <email@hidden>)
