Ed Martin

Hey, same issue here, and I *think* I found the issue, it's a mysql connector bug, specifically I am running the binary stable distribution for raspbian (2.3.0-1), from https://dl.bintray.com/openhab/apt-repo2 and...

Just wanted to say, I applied the merged from this bug and I've been running for over a month without a crash. https://github.com/openhab/openhab1-addons/pull/5699

1. mariadb 2. Right now: ` jdbc:mariadb://localhost/openhab?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC` I have tried setting serverTimeZone, connectionTimeZone, useLegacyDatetimeCode (all combinations of the three, trying UTC and America/New_York, none of it matters), switching to America/New_York...

So I think I poked around down the connector bug route, and I got it working `jdbc:mariadb://localhost/openhab?useUnicode=true&serverTimezone=America/New_York&sessionVariables=time_zone='America/New_York'` Which comes from a few things, number 1 there is a connector bug:...

@jlaur I think you don't want to use `SET time_zone`, the issue is jdbc parses the timezone from the connection parameters itself (so when you do `serverTimezone=XYZ`, the connector configures...

@jlaur So I too tried doing the conversions and I basically stumbled on the same thing, java.sql.timestamp is having a timestamp conversion being applied incorrectly. I'm going to try and...

@jlaur I think for that filterquery fix, it's JdbcDerbyDAO.java too, not just Postgres Anyways, I did more testing on this issue, looks like it is the connector, I verified that...