Databases
StackOverflow2013
Postsdbo
POWhen Does the Finally Block Run Relative to the Return
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen Does the Finally Block Run Relative to the Return
    primarykey
    data
    text
    <p>I stumbled across an interesting error yesterday and have since fixed it, but it still was bothering me this morning, so I would like to see if anyone can shed some light on the issue.</p> <p>The code in question:</p> <pre><code>final ResultSet rs = prepStatement.executeQuery(); try { if (!rs.next()) { throw new IllegalStateException("Expected non-empty result"); } return rs.getInt(0 + 1); } finally { rs.close(); } </code></pre> <p>Now for the part that doesn't make since. Every once in a while, the return statement will throw an exception indicating that getInt(int) has been called on a closed ResultSet. I verified that the prepared statement is not being closed anywhere in the code, and if the database was closing, I would see other errors as well. This leads me to believe that somehow, occasionally, the finally block is being executed before the return statement. The only thing I can think of is that the hotspot compiler doesn't always get this right. I'm using the Oracle JVM listed below.</p> <blockquote> <p>java version "1.7.0_45"<br> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)<br> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)</p> </blockquote> <p>I feel like I should mention that I have seen the host of other questions about this ordering, but they all seem to indicate that it is set in stone, where I seem to be witnessing something different.</p> <p><a href="https://stackoverflow.com/questions/15225819/try-catch-finally-return-clarification-in-java">Try-catch-finally-return clarification</a> <br> <a href="https://stackoverflow.com/questions/20164755/the-order-of-invoking-finally-block">https://stackoverflow.com/questions/20164755/the-order-of-invoking-finally-block</a> <br> <a href="https://stackoverflow.com/questions/65035/does-finally-always-execute-in-java">Does finally always execute in Java?</a> </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAlex N.
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. 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. POWhen Does the Finally Block Run Relative to the Return
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO_that somehow, occasionally, the finally block is being executed_ No, it **always** gets executed. `rs.getInt()` is executed and is stored as a return value, then `rs.close()` is executed. Then the value is returned.
      singulars
      1. POWhen Does the Finally Block Run Relative to the Return
      1. USSotirios Delimanolis
    2. COAgreed, but what I actually said was, *This leads me to believe that somehow, occasionally, the finally block is being executed before the return statement*. And that's what I would expect, but that's not what I see happening, and I'm curious why?
      singulars
      1. POWhen Does the Finally Block Run Relative to the Return
      1. USAlex N.
    3. COCan you post the exception stack trace and the name of the method your `finally` block appears in?
      singulars
      1. POWhen Does the Finally Block Run Relative to the Return
      1. USSotirios Delimanolis
 

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