问题
Some background:
I have a Java 1.6 webapp running on Tomcat 7. The database is MySQL 5.5. Previously, I was using Mysql JDBC driver 5.1.23 to connect to the DB. Everything worked. I recently upgraded to Mysql JDBC driver 5.1.33. After the upgrade, Tomcat would throw this error when starting the app.
WARNING: Unexpected exception resolving reference
java.sql.SQLException: The server timezone value 'UTC' is unrecognized or represents more than one timezone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc timezone value if you want to utilize timezone support.
Why is this happening?
回答1:
Apparently, to get version 5.1.33 of MySQL JDBC driver to work with UTC time zone, one has to specify the serverTimezone explicitly in the connection string.
jdbc:mysql://localhost/db?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
回答2:
I've solved this problem by configuring MySQL.
SET GLOBAL time_zone = '+3:00';
回答3:
If you are using Maven, you can just set another MySQL connector version (I had the same error, so i changed from 6.0.2 to 5.1.39) in pom.xml:
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.1.39</version>
</dependency>
As reported in another answers, this issue has been fixed in versions 6.0.3 or above, so you can use the updated version:
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>6.0.3</version>
</dependency>
Maven will automatically re-build your project after you save the pom.xml file.
回答4:
After reading several posts on this topic, testing different configurations and based on some insights from this mysql bug thread that's what I have understood:
- the server time zone is important in particular to convert dates stored in the database to the time zone of the application server. there are other implications but this is the most noticeable one
- GMT x UTC time zone systems. GMT was conceived in the late 19th century and can be shifted between standard time and summer time. this property could lead to a situation where the database server shifts to summer time and the application doesn't notice it (perhaps there are other complications but I didn't research further). UTC does not vary over time (it is always within about 1 second of mean solar time at 0° longitude).
- serverTimeZone definition was introduced in mysql jdbc connectors versions 5.1 ahead. until version 8 it could be ignored with
useLegacyDatetimeCode=true, which in conjunction withuseJDBCCompliantTimezoneShift=truewould make the application get the database time zone on every connection. In this mode GMT time zones such as 'British Summer Time' would be converted to the internal java/JDBC format. New time zones could be defined in a .properties file such as this one - Starting with jdbc driver version 8, automatic time matching (
useJDBCCompliantTimezoneShift) and legacy time format (useLegacyDatetimeCode) were removed (see mysql jdbc connector changelog). therefore setting these 2 parameters has no effect as they are completely ignored (new default isuseLegacyDateTimeCode=false) - In this manner setting
serverTimezonebecame mandatory if any of the time zones (application/database servers) are not in the format 'UTC+xx' or 'GMT+xx' - There is no impact of setting server time as UTC (for instance with
jdbc:mysql://localhost:3306/myschema?serverTimezone=UTC, even if your application / database servers are not in this timezone. The important is for the application connection string + database to be synchronized with the same time zone. In different words, simply setting serverTimezone=UTC with a different time zone on the database server will shift any dates extracted from the database - The MySQL default time zone can be set to UTC+0 with the my.ini or my.cnf files (windows / linux respectively) by adding the line
default-time-zone='+00:00'(details in this StackOverflow post) - Databases configured on AWS (amazon web services) are automatically assigned UTC+0 default time (see AWS help page here)
回答5:
The connection string should be set like this:
jdbc:mysql://localhost/db?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
If you are defining the connection in an xml file (such as persistence.xml, standalone-full.xml, etc..), instead of & you should use & or use a CDATA block.
回答6:
This is a bug in mysql-connector-java from version 5.1.33 to 5.1.37. I've reported it here: http://bugs.mysql.com/bug.php?id=79343
Edited: This has been corrected from mysql-connector-java 5.1.39
It was a typo in TimeUtil class in loadTimeZoneMappings method that raises a NPE locating /com/mysql/jdbc/TimeZoneMapping.properties file. If you look at the code, the file should be located within TimeUtil class loader, not TimeZone:
TimeUtil.class.getResourceAsStream(TIME_ZONE_MAPPINGS_RESOURCE);
The parameter useLegacyDatetimeCode allows to correct the difference between client and server timezones automatically when using dates. So it helps you precissely not having to specify timezones in each part. Althought using serverTimeZone parameter is a workaround, and meanwhile the patch is released, you can try better correcting the code by yourself as I did.
If it's a standalone application, you can try simply to add a corrected com/mysql/jdbc/TimeUtil class to your code and be careful with jar loading order. This can help: https://owenou.com/2010/07/20/patching-with-class-shadowing-and-maven.html
If it's a web application, the easier solution is to create your own mysql-connector-java-5.1.37-patched.jar, substituting the .class directly into the original jar.
回答7:
I solved putting below connection string in the URL
jdbc:mysql://localhost:3306/db?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
回答8:
It worked for me just by adding serverTimeZone=UTC on application.properties.spring.datasource.url=jdbc:mysql://localhost/db?serverTimezone=UTC
回答9:
I added in mysql config file in section [mysqld]
default_time_zone='+03:00'And restart mysql server:
sudo service mysql restart
Where +03:00 my UTC time zone.
Path to config file on my os ubuntu 16.04:
/etc/mysql/mysql.conf.d/mysqld.cnf
WARNING: IF YOUR TIME ZONE HAVE SUMMER AND WINTER TIME. YOU MUST CHANGE UTC IN CONFIG IF CHANGE TIME. TWICE IN YEAR(USUALLY) OR SET CRONTAB WITH SUDO.
My url jdbc connection:
"jdbc:mysql://localhost/java"
回答10:
I have the same problem and i solved it append only "?serverTimezone=UTC" to my string connection.
#sinossi my problem:
java.sql.SQLException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
my dbDriver = com.mysql.jdbc.Driver
my jar = mysql-connector-java-8.0.12.jar
my java = 1.8
my tomcat = Apache Tomcat Version 8.5.32
my MySql server = MySql ver.8.0.12
回答11:
The above program will generate that time zone error.
After your database name you have to add this: ?useTimezone=true&serverTimezone=UTC. Once you have done your code will work fine.
Best of luck :)
回答12:
Everything that we need to fix the problem with serverTimezone:
String url = "jdbc:mysql://localhost:3306/db?serverTimezone=" + TimeZone.getDefault().getID()
回答13:
I'm using mysql-connector-java-8.0.13 and had the same problem. I created my database in the command line console and solved this problem by using @Dimitry Rud's solution on the command line:
SET GLOBAL time_zone = '-6:00';
I didn't need to restart anything, set the time and immediately run my code in eclipse, it connected with no problems.
The bug is supposed to be fixed in an older version, but I think I got this error because after I created the database in the console, I didn't set this. I'm not using workbench nor another app to manage this rather than the console.
回答14:
I executed following on my database side.
mysql> SET @@global.time_zone = '+00:00';
mysql> SET @@session.time_zone = '+00:00';
mysql> SELECT @@global.time_zone, @@session.time_zone;
I am using Server version: 8.0.17 - MySQL Community Server - GPL
source: https://community.oracle.com/thread/4144569?start=0&tstart=0
回答15:
This worked for me.
on DBeaver 6.0 : Go to Connection Settings > Driver Properties > Server Time Zone > Set UTC.
Also, in spring boot config, had to set below property.
jdbc:mysql://localhost:/?serverTimezone=UTC
回答16:
You can use the MySQL connector in the Maven dependency,
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>8.0.14</version>
</dependency>
Then you need the set the right parameters in the application.properties file,
spring.datasource.url=jdbc:mysql://localhost:3306/UserReward?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
spring.datasource.username=testuser
spring.datasource.password=testpassword
# MySQL driver
spring.datasource.driverClassName=com.mysql.jdbc.Driver
spring.jpa.database-platform=org.hibernate.dialect.MySQL5Dialect
回答17:
From mysql workbench run the following sql statements:
- SET @@global.time_zone = '+00:00';
- SET @@session.time_zone = '+00:00';
with the following sql statements check if the values were set:
SELECT @@global.time_zone, @@session.time_zone;
回答18:
I also was having the exact same problem in LibreOffice Base. So I just specified a non 'daylight savings time zone' in the connection string.
I tried without the "&serverTimezone=MST" but that failed as well.
I also tried "&serverTimezone=MDT" and that failed, so for some reason, it doesn't like daylight savings time!
回答19:
I had the same problem when I try to work with spring boot project on windows.
Datasource url should be:
spring.datasource.url=jdbc:mysql://localhost/database?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC
回答20:
I solved this issue without any single code change. just goto system time setting and set the time zone. In my case the default time zone was UTC which I changed to my local time zone. After I did restart all services, everything worked for me.
回答21:
I am late, But If you are struggling through the following error and using datasource(javax.sql.DataSource):
The server time zone value 'CEST' is unrecognized or represents more than one time zone.
Set following line to get rid of the error:
MysqlDataSource dataSource = new MysqlDataSource();
dataSource.setServerTimezone("UTC");
回答22:
In my case, it was a test environment and I had to make an existing application to work without any configuration changes, and if possible without any MySQL config changes. I was able to fix the issue by following @vinnyjames suggestion and changing server timezone to UTC:
ln -sf /usr/share/zoneinfo/UTC /etc/localtime
service mysqld restart
Doing that was enough for me to solve the issue.
回答23:
Agree with @bluecollarcoder answer, but it's better to use TimeZone.getDefault().getID(); at the end of the connection string:
"jdbc:mysql://localhost/db?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=" + TimeZone.getDefault().getID();
In this case Timezone parameter automatically updates depending on the local machine timezone.
回答24:
I also got the same running java JDBC in NetBeans. This is how it fixed
I use Xampp. In conf button of Apache I opened httpd.conf file and on first line I typed
# Set timezone to Europe/Athens UTC+02:00
SetEnv TZ Europe/Athens.
In conf button of MySQL I opened my.ini file and on last line I typed "Europe/Athens"
Stopped and started both Apache and MySQL
Problem fixed.
*(Local mechine time zone is different, but no problem.)
来源：https://stackoverflow.com/questions/26515700/mysql-jdbc-driver-5-1-33-time-zone-issue