title: Is throwing an exception inside a finally block a performance issue?
body: <p>In Rational Application Developer(RAD based on eclipse), under software analyzer, I see a code review comment (under Performance =>Memory section) saying "Avoid the throw statement inside of finally".</p>
  
  <p><strong>How does defining throw inside a finally block affect performance?</strong></p>
  
  <p><a href="https://i.stack.imgur.com/hc9If.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hc9If.jpg" alt="enter image description here"></a></p>
  
  <p>Here is code snippet, we have already suggested to change code to log exception trace and do not throw exception, </p>
  
  <pre><code>     } finally {
          if (bufferedReader != null) {
              try {
                  bufferedReader.close();
              } catch (final IOException ex) {
                  throw ex;
              }
          }
      }
  </code></pre>
  
  <p>I was just wondering how this could affect memory and performance?</p>