# Why does Logstash not restart from JDBC I/O errors?

**URL:** <https://discuss.elastic.co/t/why-does-logstash-not-restart-from-jdbc-i-o-errors/114422>\
**Category:** Logstash\
**Created:** [January 7, 2018, 7:43pm UTC](https://discuss.elastic.co/t/why-does-logstash-not-restart-from-jdbc-i-o-errors/114422 "2018-01-07T19:43:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [January 8, 2018, 11:03am UTC](https://discuss.elastic.co/t/why-does-logstash-not-restart-from-jdbc-i-o-errors/114422/2 "2018-01-08T11:03:44Z")

</div>

What version of the JDBC input are you using? `bin/logstash-plugin list --verbose | grep jdbc` or similar.

This version `4.3.0` was refactored to open and close connections for each trip to the db (each scheduled run)

---

_[View the full topic](https://discuss.elastic.co/t/why-does-logstash-not-restart-from-jdbc-i-o-errors/114422)._