# TZInfo::AmbiguousTime exception when parsing JDBC column **URL:** \ **Category:** Logstash\ **Created:** [November 7, 2017, 7:42pm UTC](https://discuss.elastic.co/t/tzinfo-ambiguoustime-exception-when-parsing-jdbc-column/106748 "2017-11-07T19:42:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![obodard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/obodard/32/27575_2.png) [@obodard](https://discuss.elastic.co/u/obodard)\ **Post date:** [November 7, 2017, 7:42pm UTC](https://discuss.elastic.co/t/tzinfo-ambiguoustime-exception-when-parsing-jdbc-column/106748/1 "2017-11-07T19:42:45Z")
I am getting this exception when getting my data with the JDBC plugin: error: 26413962 Sequel::InvalidValue TZInfo::AmbiguousTime: 2017-11-05T01:30:00+00:00 is an ambiguous local time. This is probably because I am already converting my timezone in my JDBC plugin with this parameter: jdbc\_default\_timezone =\> "America/New\_York" Therefore 1:30am happened twice on November 5th, and I suspect Logstash doesn't know what to do and it fall in an infinite loop. As a workaround, I removed the jdbc\_default\_timezone parameter and instead I convert my values in UTC in the select statement, like this: DATEADD(hh, DATEDIFF(hh, GETDATE(), GETUTCDATE()), th.[DueDate]) as DueDate But this workaround is annoying since I need to modify all of my logstash inputs date columns. Is there a way to force it to pick any of the two possible times, or any other way? Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 5, 2017, 7:42pm UTC](https://discuss.elastic.co/t/tzinfo-ambiguoustime-exception-when-parsing-jdbc-column/106748/2 "2017-12-05T19:42:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.