StreamCorruptedException - what is causing it?

Question

I am developing a networked multiplayer game in Java, but I am having problems when it comes to sending data around the network. The game will run fine for a seemingly random amount of time (usually between about 10 seconds and 2 minutes) before a StreamCorruptedException occurs in each of the clients. 90% of the time the message says "invalid type code: 00" but sometimes I get "invalid handle value" or various others.
I have searched for ages for more information on this, but there isn't much help available. I have tried a couple of things suggested in other threads, to no avail.
The code that listens for connections from clients:
while(numConnections < MAX_CONNECTIONS) {
    socket = serverSocket.accept();
    numConnections++;
    System.out.println("Connection from " +socket.getInetAddress());
    ServerThread thread = new ServerThread(socket);+
    thread.start();
}The ServerThread class handles each connection and contains the following method which is used to send objects to all connected clients:+
public static void sendToClients(Object o) {
    try {
        for(int i = 0; i < connections.size(); i++) {
            ServerThread thread = connections.elementAt(i);
            thread.out.writeObject(o);
            thread.out.flush();
catch(IOException e) {
    e.printStackTrace();
}The Client class reads the objects sent by the server:
try {
            Object o;
            while(true) {
                o = inputStream.readObject();
}The exception occurs in the o = inputStream.readObject() line
Sorry about the bad formatting... first post and for some reason the input box jumps all over the place when I'm typing so I can't see what's being written!
Edited by: interdreamuk on Feb 23, 2010 9:48 AM

Answer 1

No, I haven't seen AC yet... only one input and output stream is created per socket and used for the life of that socket. The most common code I get is 00, but I have also seen 23 and 79. I tried searching for a list of what the codes mean, but can't find much info about the causes of this exception at all really. I know it gets thrown when "Control information in the stream is inconsistent" according to the API, but that doesn't really help much.
Also, after reading about this for hours, I changed writeObject to writeUnshared (just a shot in the dark really), which for some reason seems to have significantly increased the amount of time for which the application will run before the exception occurs.
Edited by: interdreamuk on Feb 24, 2010 12:46 AM