# Logstash External Component Retry Attempts

**URL:** <https://discuss.elastic.co/t/logstash-external-component-retry-attempts/202738>\
**Category:** Logstash\
**Created:** [October 8, 2019, 10:57pm UTC](https://discuss.elastic.co/t/logstash-external-component-retry-attempts/202738 "2019-10-08T22:57:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [October 9, 2019, 2:18pm UTC](https://discuss.elastic.co/t/logstash-external-component-retry-attempts/202738/2 "2019-10-09T14:18:38Z")

</div>

The connect! call has a [rescue/retry loop](https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/blob/4df5dca57cfaefdbdbbcd96c4f872272ea12c2f9/lib/logstash/plugin_mixins/rabbitmq_connection.rb#L161) that will run forever. The connect! call never ends unless rabbitmq becomes available (or you send a second SIGTERM).

---

_[View the full topic](https://discuss.elastic.co/t/logstash-external-component-retry-attempts/202738)._