ansaurus

Question

Answer 1

+1 A:

Do you have the code for

  Main.runAClient();

perhaps somebody is catching that exception and logging it, and then rethrowing?

djna 2010-01-11 14:13:02

Indeed it is being logged, see here: http://stackoverflow.com/questions/2041817/gui-problemnetwork-problem

laura 2010-01-11 14:15:29

ahahaha, laura, awesome..

Bozho 2010-01-11 14:16:30

Answer 2

+3 A:

You posted the code in your previous question: http://stackoverflow.com/questions/2041817/gui-problemnetwork-problem

Judging by the runAClient method, you are logging the exception and eating it up (not throwing it further).

public static void runAClient() {
    try {
        c = new Socket("localhost", 5000);
    } catch (UnknownHostException ex) {
        Logger.getLogger(Main.class.getName()).log(Level.SEVERE, null, ex);
    } catch (IOException ex) {
        Logger.getLogger(Main.class.getName()).log(Level.SEVERE, null, ex);
    }
}

The second catch (IOException) should not log and should throw the exception. Actually, you probably want to split that catch into a ConnectException catch which you would throw and a IOException catch which you can handle separately.

Edit: I'll extend this a bit. ConnectException extends RemoteException which in turn extends IOException, which you are catching and logging in your runAClient method. You can do two things:

remove the IOException altogether, and catching it at an upper level (a solution which is very ugly in my opinion)

or

split the IOException block into two catch blocks, one for the ConnectException, in which you just throw, and one for the rest of the IOExceptions, which you can log (or handle differently) - just make sure the ConnectException block is written before the IOException block

laura 2010-01-11 14:19:35

(+1), just be explicit about ConnectionException extending IOException, hence being caught.

Bozho 2010-01-11 14:22:31

I have done it but it did like as before[:(]

Johanna 2010-01-11 14:44:01

@Johanna: What exactly are you asking? Laura has shown how to restructure your code to not swallow the exception. Are you asking why the exception is actually happening?

Adamski 2010-01-11 14:59:12

ansaurus

tags:

views:

answers:

How can we handle the ConnectException?

related questions