why would version == SocketWarpper.CLOSING ?

[mazz]

What would cause the version read over the wire to be SocketWrapper.CLOSING?

Specifically, I'm looking at MicroSocketClientInvoker, line 629-ish from Remoting 2.2.2.SP8:

if (version == SocketWrapper.CLOSING)
{
 log.debug("Received version 254: treating as end of file");
 throw new SocketException("end of file");
}

I'm sending a message from a client, and I see no reason why this should be failing, but it does. The failure is due to that exception getting thrown above. I'm not sure what it means or what could cause it to happen. Any tips would be appreciated. :}

[mazz]

FWIW, I did read:

http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4134761#4134761

but this is happening consistently - its not like its a socket timeout or it does this sporadically. This happens every time I try to send a message in this one particular place in my code (where everywhere else, it is working).

I'm trying to find out what's different between the code that works and the code that doesn't.

[ron_sigal]

Hi John,

SocketWrapper.CLOSING should be sent only when a ServerThread shuts down and closes its socket. What's going on on the server side?

-Ron

[mazz]

Ron,

Ah.. I see it. On the server side, the message was received, but the de-serialization of one of my incoming objects within the message failed. Hence, the server socket closes immediately and hence why I get the error that I do on the client side.

This looks like its a problem on my end. In short, I need to make sure I send an object that is de-serializable on the server.

[ron_sigal]

http://www.fortunecity.com/lavender/tombstone/839/simpsons/Monty_excellent.wav