Path: csiph.com!aioe.org!.POSTED!not-for-mail
From: Steven Simpson <ss@domain.invalid>
Newsgroups: comp.lang.java.programmer
Subject: Re: Strange Socket problem
Date: Thu, 01 Mar 2012 20:59:49 +0000
Organization: Aioe.org NNTP Server
Lines: 27
Message-ID: <5j4529-ln2.ln1@s.simpson148.btinternet.com>
References: <jiojsa$5ol$1@dont-email.me>
NNTP-Posting-Host: SYma/1Oij9bhI+errvtPhg.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:12563

On 01/03/12 19:49, Knute Johnson wrote:
> It does print the "SportsWinClient Disconnected" message but never 
> executes the "fireconnectionEvent()" method after creating a new 
> Socket.  It doesn't print any Exception message.  I'm not sure how it 
> gets out of the try block without printing the "End of Stream" message 
> or an exception message.

Can you provide an exact trace of the messages that are visible in the 
code you've shown (around the problematic event, of course), just so 
there's no ambiguity about what you're seeing?

>                 System.out.println("SportsWinClient: End of Stream");
>             } catch (IOException ioe) {
>                 System.out.println("SportsWinClient: " + ioe.toString());

Catch Throwable here too, print it out, and rethrow, so we can be sure 
no other exception is slipping through.

>             } finally {
>                 isConnected = false;
>                 if (socket != null)
>                     try {


-- 
ss at comp dot lancs dot ac dot uk