title: Resilience4j.retry with exception is not working
body: <p>I am using <a href="https://resilience4j.readme.io/docs/retry" rel="nofollow noreferrer">resilience4j.retry</a> with <a href="https://resilience4j.readme.io/docs/circuitbreaker" rel="nofollow noreferrer">resilience4j.circuitbreaker</a>. <code>Service1</code> is calling another service <code>Service2</code>, which can throw exceptions. Even if I get exceptions, I should try to connect for at least defined no of times <code>waitDuration * maxRetryAttempts</code>. </p>
  
  <blockquote>
    <p>Service1 --->    calling   ---> Service2</p>
  </blockquote>
  
  <p><strong>application.yml</strong> </p>
  
  <pre><code>resilience4j.retry:
    instances:
      service1:
        maxRetryAttempts: 4
        waitDuration: 1000 #ms
        retryExceptions:  
          - org.apache.http.conn.HttpHostConnectException
          - org.apache.thrift.TException
          - java.net.ConnectException
  </code></pre>
  
  <p><strong>Service1Repository.java</strong></p>
  
  <pre><code>Service2Response response = CircuitBreaker.decorateSupplier(circuitBreaker,
                                      Retry.decorateSupplier(retry, () -&gt; {
                                          try {
                                              return service2.getdata(params);
                                          } catch (TException e) {
                                              log.error("msg", e);
                                              throw new Service1Exception("msg", e);
                                          }
                                      })
                              ).get();
  </code></pre>
  
  <p>However, when <code>Service2</code> is down, it is not retrying (max 4 times, each after 1000ms should happen) I am getting a response (<code>null</code> in my case) immediately. I tried with increasing values (10000ms), still the same. I am seeing logs are printed but service should wait for <code>waitDuration * maxRetryAttempts</code> if <code>Serviece2</code> is down. </p>