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 Newsgroups: comp.lang.java.programmer Subject: Re: streaming problem and thread freeze Followup-To: comp.lang.java.programmer Date: Wed, 11 May 2011 14:06:44 +1200 Organization: Geek Central Lines: 23 Message-ID: References: <005a9e79-36fe-4bf1-aa1d-bda3a5aaebf2@glegroupsg2000goo.googlegroups.com> 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 1305079604 32128 118.92.95.178 (11 May 2011 02:06:44 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Wed, 11 May 2011 02:06:44 +0000 (UTC) User-Agent: KNode/4.4.7 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3947 In message , Daniele Futtorovic wrote: > On 10/05/2011 05:31, Lawrence D'Oliveiro allegedly wrote: > >> In message, 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. > > It would be yet much easier, as you perhaps one day will learn, to > realise that checked exceptions are not a bother, but an almost > invaluable tool. So how does that help in this case?