I’ve just come across this but not sure if it’s strictly a problem. It seems WrapperOptions#getJdbcTimeZone() is used to create a java.util.Calendar instance with the time zone which is passed into ResultSet#rs.getTimestamp(String, Calendar) which means the resulting Instant is correct, but you get it converted into the runtime default zone.