Bug #93871 JDBC connection is failing due to server time zone value is set to 'PDT'
Submitted: 10 Jan 2019 5:45 Modified: 10 Jan 2019 11:39
Reporter: kriti suwalka Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / J Severity:S1 (Critical)
Version:8.0.12 OS:Any
Assigned to: CPU Architecture:Any

[10 Jan 2019 5:45] kriti suwalka
Description:
We are trying to establish a JDBC connection to MySQL community server version 5.5.34 and server has a PDT time zone. Connection is failing with following error
java.sql.SQLException: The server time zone value 'PDT' 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.

Please note that it used to work fine with 5.x series drivers and we have recently upgraded the driver to 8.0.12 version and all our connections started failing with the mentioned error.
We have gone through https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-other-changes.html article to check what has been changed in 8.x driver from 5.x driver and it doesn't say anything about the behavior we are seeing. However, it says that if timezone is not supported by java, override it using serverTimezone property. So we set the property to "Pacific Daylight Time" but it again failed with "No timezone mapping entry for 'Pacific Daylight Time'" error. I extracted the mysql-connector-java-8.0.12.jar file and check that com\mysql\cj\util\TimeZoneMapping.properties does have an entry for "Pacific Daylight Time" (check following entry)
Pacific\ Daylight\ Time=America/Los_Angeles

So I expected it to map Pacific Daylight Time to America/Los_Angeles as per the mapping and the connection to go through fine but it is failing with no entry found error. 
It's really critical for us and we need a clarification.

How to repeat:
Try to establish a connection to a DB which is configured with PDT timezone.
[10 Jan 2019 11:40] MySQL Verification Team
Hello kriti,

Thank you for the report.
Imho this is duplicate of Bug #85816, please see Bug #85816

thanks,
Umesh