Are <elrond at ctemp.dhs.org> writes: > But the JVM_recv thingy could be something else, I did some research on it > and one forum suggested that the VM bound the socket to an already bound > port.
No, that would be an EADDRINUSE error from bind(). When a connection is already in progress, the system doesn't suddenly decide that there is an address conflict. Believe it or not, when your peer closes the connection, it can look exactly like this: recv() fails with an ECONNRESET error, which translates to "Connection reset by peer". This seemd to have happened in your JVM_recv function. (I'm assuming a POSIX system. A windows VM could work differently.) -- Robbe -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.ng Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20011213/a90ee694/attachment.pgp>
