Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!news.snarked.org!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail
From: Lawrence D'Oliveiro <ldo@geek-central.gen.new_zealand>
Newsgroups: comp.lang.java.programmer
Subject: Re: streaming problem and thread freeze
Followup-To: comp.lang.java.programmer
Date: Tue, 10 May 2011 15:31:27 +1200
Organization: Geek Central
Lines: 13
Message-ID: <iqabig$i1u$1@lust.ihug.co.nz>
References: <005a9e79-36fe-4bf1-aa1d-bda3a5aaebf2@glegroupsg2000goo.googlegroups.com> <iq9ai7$t2s$1@dont-email.me>
NNTP-Posting-Host: 118-92-95-178.dsl.dyn.ihug.co.nz
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Trace: lust.ihug.co.nz 1304998288 18494 118.92.95.178 (10 May 2011 03:31:28 GMT)
X-Complaints-To: abuse@ihug.co.nz
NNTP-Posting-Date: Tue, 10 May 2011 03:31:28 +0000 (UTC)
User-Agent: KNode/4.4.7
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3890

In message <iq9ai7$t2s$1@dont-email.me>, Daniele Futtorovic wrote:

> Secondly, although it is only a minor thing and only my personal
> opinion, this:
> 
>    } catch (IOException ex) {
>      log.severe(ex.getMessage());
>    }
> 
> is a *very* bad idea. Log the full stack.

It would be so much easier if you could simply not bother to catch the 
exception at all, and let your program crash with a full stack trace.