http://www.fortunecity.com/lavender/tombstone/839/simpsons/Monty_excellent.wav
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269121#4269121
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269121
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. I
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
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269119#4269119
Reply to the post :
http://www.jboss.org/index.
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 everywhe
