Thread: alot of Exceptions from logging out?!? HELP MEH

Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1. #1 alot of Exceptions from logging out?!? HELP MEH 
    Banned

    Join Date
    May 2008
    Posts
    2,327
    Thanks given
    55
    Thanks received
    67
    Rep Power
    0
    Code:
    - SilabGarza v9 - Online -
    Gir logged on.
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    java.net.SocketException: Software caused connection abort: recv failed
            at java.net.SocketInputStream.socketRead0(Native Method)
            at java.net.SocketInputStream.read(Unknown Source)
            at java.net.SocketInputStream.read(Unknown Source)
            at client.packetProcess(client.java:18692)
            at PlayerHandler.process(PlayerHandler.java:155)
            at server.main(server.java:73)
    Game saved for player Gir
    Playr Gir Logged out.
    thats wat happens when i hit log out button....

    as u can see, i logged in
    then i hit the logout button
    then it spammed all those socket exceptions...

    ANYONE NO HOW TO FIX?!
    Reply With Quote  
     

  2. #2  
    Registered Member blood rush20's Avatar
    Join Date
    Sep 2008
    Posts
    426
    Thanks given
    18
    Thanks received
    9
    Rep Power
    7
    called debugging trace all those back to where they go 1 is client.java line 18692 umm i say if you did anything look at code make sure it don't after the logout
    Reply With Quote  
     

  3. #3  
    Registered Member

    Join Date
    Jun 2007
    Posts
    2,237
    Thanks given
    267
    Thanks received
    411
    Rep Power
    1283
    If just means that you've closed the socket while data is still been processed
    Don't worry, Be happy.
    Reply With Quote  
     

  4. #4  
    Registered Member
    Whired's Avatar
    Join Date
    Aug 2007
    Posts
    2,126
    Thanks given
    238
    Thanks received
    500
    Rep Power
    822
    Quote Originally Posted by Daniel View Post
    If just means that you've closed the socket while data is still been processed
    What he said.


    In your log out case, make sure the Socket.close(); is right before "break;"
    Socket is usually given the name "s" so it will probably look like
    Code:
    s.close();
    Reply With Quote  
     

  5. #5  
    Banned

    Join Date
    May 2008
    Posts
    2,327
    Thanks given
    55
    Thanks received
    67
    Rep Power
    0
    eh well power went out for 5 minutes here.... so the dedi comp got glitcheed, restarting the computer now, il post those lines after i get access to them again....
    Reply With Quote  
     

  6. #6  
    Banned

    Join Date
    May 2008
    Posts
    2,327
    Thanks given
    55
    Thanks received
    67
    Rep Power
    0
    this is line 18692...

    Code:
        public boolean packetProcess() {
            try {
                if (timeOutCounter++ > 20) { 
                    actionReset();
    		savefile = true;
                    disconnected = true;
                    return false;
                }
                if(in == null)  return false;
    	    int avail = in.available();
                if(avail == 0) return false;
                if(packetType == -1) {
                    packetType = in.read() & 0xff;
                    if(inStreamDecryption != null)
                        packetType = packetType - inStreamDecryption.getNextKey() & 0xff;
                    packetSize = packetSizes[packetType];
                    avail--;
                }
                if(packetSize == -1) {
                    if(avail > 0) {
                        packetSize = in.read() & 0xff;
                        avail--;
                    }
                    else return false;
                }
                if(avail < packetSize) return false;
                fillInStream(packetSize);
                timeOutCounter = 0;
                parseIncomingPackets();
                packetType = -1;
            } catch(java.lang.Exception __ex) {
                __ex.printStackTrace();
    	    savefile = true; 
                disconnected = true;
    	  } return true;
    	}
    Reply With Quote  
     

  7. #7  
    Registered Member

    Join Date
    Jun 2007
    Posts
    2,237
    Thanks given
    267
    Thanks received
    411
    Rep Power
    1283
    Yes the error means some part of your software
    Code:
    if (timeOutCounter++ > 20) { 
                    actionReset();
    		savefile = true;
                    disconnected = true;
                    return false;
                }
    That part, cause the socket to close whilst data processing is still been done.
    Don't worry, Be happy.
    Reply With Quote  
     

  8. #8  
    Registered Member
    craig903's Avatar
    Join Date
    Sep 2007
    Age
    30
    Posts
    1,357
    Thanks given
    14
    Thanks received
    92
    Rep Power
    238
    Just remove the __ex.printStackTrace if you want to take the easy root.

    } catch(java.lang.Exception __ex) {
    __ex.printStackTrace();

    Otherwise .....
    Visit Rune Miracle Here
    Reply With Quote  
     

  9. #9  
    Registered Member

    Join Date
    Jun 2007
    Posts
    2,237
    Thanks given
    267
    Thanks received
    411
    Rep Power
    1283
    The error will still occur, your just removing the console debuging.
    Don't worry, Be happy.
    Reply With Quote  
     

  10. #10  
    Registered Member
    Whired's Avatar
    Join Date
    Aug 2007
    Posts
    2,126
    Thanks given
    238
    Thanks received
    500
    Rep Power
    822
    Quote Originally Posted by silabgarza View Post
    this is line 18692...

    Code:
        public boolean packetProcess() {
            try {
                if (timeOutCounter++ > 20) { 
                    actionReset();
    		savefile = true;
                    disconnected = true;
                    return false;
                }
                if(in == null)  return false;
    	    int avail = in.available();
                if(avail == 0) return false;
                if(packetType == -1) {
                    packetType = in.read() & 0xff;
                    if(inStreamDecryption != null)
                        packetType = packetType - inStreamDecryption.getNextKey() & 0xff;
                    packetSize = packetSizes[packetType];
                    avail--;
                }
                if(packetSize == -1) {
                    if(avail > 0) {
                        packetSize = in.read() & 0xff;
                        avail--;
                    }
                    else return false;
                }
                if(avail < packetSize) return false;
                fillInStream(packetSize);
                timeOutCounter = 0;
                parseIncomingPackets();
                packetType = -1;
            } catch(java.lang.Exception __ex) {
                __ex.printStackTrace();
    	    savefile = true; 
                disconnected = true;
    	  } return true;
    	}

    It isn't actually the fault of that line. The fault is that your log out method is messed up (either missing something or out of order) and
    Code:
    packetProcess()
    is running after the socket has been closed. You need to make sure your log out method stops everything that has to do with the current client before closing the socket.

    Quote Originally Posted by q a z7o View Post
    Just remove the __ex.printStackTrace if you want to take the easy root.
    What he said is true too. The only negative effects of doing this is that if you need to save something or do something a bit after the socket is closed, it will never work. Also, any indisposed objects will be held in the JVM until the next garbage collect.
    Reply With Quote  
     

Page 1 of 2 12 LastLast

Thread Information
Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)


User Tag List

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •