Observed so far only under Windows98 first edition --
others not yet tested. If this bug also occurs in later
versions of Windows, then we should upgrade the priority.
When closing my laptop, it goes into "suspend" mode.
There are probably other actions that can cause this on
this or other PCs. When revived from suspend mode,
external *and internal* TCP connections seem to be
broken, and all Sockets seem to be broken as well.
(This has been seen just now in JDK1.3.1, but has also
been seen in earlier JDKs.) I have no idea whether this
is a Windows problem or a Java-on-Windows problem, but
in any case, we need to survive it.
Running vats should experience nothing worse than a
partition. So the connection breakage is fine. But
VatTP needs to recover the Socket on which it listens
for new connections. Or should some recovery action
instead be taken at the CapTP level?
Log in to post a comment.
