Databases
StackOverflow2013
Postsdbo
POException from resource close in finally hides another -- who cares?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POException from resource close in finally hides another -- who cares?
    primarykey
    data
    text
    <p>Firstly, sorry for asking a question on what must be a well-worn topic. I've come across loads of questions with answers suggesting to swallow (catch and ignore/log) potential exception from methods that close resources in finally blocks. It seems to be a generally accepted pattern. But I haven't yet seen anybody explain <em>why</em>. Here's just one example: <a href="https://stackoverflow.com/questions/1335812/try-catch-finally-and-then-again-a-try-catch">Try-catch-finally and then again a try catch</a>.</p> <p>I understand that any exception thrown from a finally block will "mask" any exception thrown in the corresponding try block, but I don't see why this is a bad thing. For example:</p> <pre><code>Resource r = new Resource(); try { r.use(); other(); } finally { r.close(); } </code></pre> <p>My current understanding is:</p> <ol> <li>If only <code>close</code> throws an exception, we definitely don't want to swallow it.</li> <li>If both <code>use</code> and <code>close</code> throw an exception, it's probably for the same underlying reason, and it doesn't matter which exception gets propagated up (they both would contain equally useful information?).</li> <li>If both <code>other</code> and <code>close</code> throw an exception, there are two unrelated problems. Arguably the one that happened first should propagate, but there isn't any reason to suggest that the first exception <em>caused</em> the second (is there?), so either will do.</li> </ol> <p>What am I wrong about?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAmyGamy
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POException from resource close in finally hides another -- who cares?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POException from resource close in finally hides another -- who cares?
      1. USfastcodejava
      1. VTFavorite
    3. VO
      singulars
      1. POException from resource close in finally hides another -- who cares?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload