# Logstash jdbc scheduler issue

**URL:** <https://discuss.elastic.co/t/logstash-jdbc-scheduler-issue/65774>\
**Category:** Logstash\
**Created:** [November 11, 2016, 8:44am UTC](https://discuss.elastic.co/t/logstash-jdbc-scheduler-issue/65774 "2016-11-11T08:44:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jayadeep\_Reddy](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@Jayadeep\_Reddy](https://discuss.elastic.co/u/Jayadeep_Reddy)\
**Post date:** [November 11, 2016, 8:44am UTC](https://discuss.elastic.co/t/logstash-jdbc-scheduler-issue/65774/1 "2016-11-11T08:44:30Z")

</div>

when the network glitches the scheduler is not trying to open the new connection. It is always returning the below error even if the network is Up

←[33mException when executing JDBC query {:exception=\>#\<Sequel::DatabaseError: J  
ava::JavaSql::SQLException: [NetSuite][SuiteAnalytics Connect JDBC Driver]Intern  
al network error, connection closed.\>, :level=\>:warn}←[0m  
←[31mJava::JavaSql::SQLException: [NetSuite][SuiteAnalytics Connect JDBC Driver]  
Internal network error, connection closed.:

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 13, 2016, 7:57am UTC](https://discuss.elastic.co/t/logstash-jdbc-scheduler-issue/65774/2 "2016-11-13T07:57:42Z")

</div>

What version?  
What OS?  
What does your config look like?

Please provide more information.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 11, 2016, 7:57am UTC](https://discuss.elastic.co/t/logstash-jdbc-scheduler-issue/65774/3 "2016-12-11T07:57:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.