# JDBC Timestamp doesn't refresh, leads to large queues

**URL:** https://discuss.elastic.co/t/jdbc-timestamp-doesnt-refresh-leads-to-large-queues/278393
**Category:** Logstash
**Created:** [July 12, 2021, 8:55am UTC](https://discuss.elastic.co/t/jdbc-timestamp-doesnt-refresh-leads-to-large-queues/278393 "2021-07-12T08:55:45Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![chris\_ts24](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_ts24/32/79048_2.png) [@chris\_ts24](https://discuss.elastic.co/u/chris_ts24)
#### Post date: [July 15, 2021, 3:00pm UTC](https://discuss.elastic.co/t/jdbc-timestamp-doesnt-refresh-leads-to-large-queues/278393/6 "2021-07-15T15:00:11Z")

</div>

To anyone who is interested in the topic, I've localized the failure to update the jdbc timestamps to a Rufus Scheduler Error. I've opened a new topic [here](https://discuss.elastic.co/t/rufus-scheduler-error-tzinfo-periodnotfound/278811).

---

_[View the full topic](https://discuss.elastic.co/t/jdbc-timestamp-doesnt-refresh-leads-to-large-queues/278393)._