Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Cannot create MySQL Datasource

Description

Any attempt to create a MySQL Datasource results in this error message and the inability to complete the setup:

"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."

Attempting to set the TIMEZONE setting within the config has no effect, otherwise it's left at the default. All other settings are at default values. Username and password are correct and tested elsewhere. I've attempted this from both the SERVER and WEB admin consoles, same result.

I've restarted LUCEE and MySQL and I still get the same result. I've upgraded MySQL from 5.7.18 to 5.7.21 and still get the same result.

I tried (via the Application Extensions Console) to downgrade the JDBC driver from version 8.0.9 to 6.0.6 and still get the same result.

Environment

Mac OS 10.13.4, MySQL versions 5.7.18 and 5.7.21, Java version: 1.8.0_131 (Oracle Corporation) 64bit, Tomcat version: 8.0.36, JDBC Driver versions: 6.0.6 and 8.0.9, Lucee 5.2.6.60 (express).

Attachments

1
  • 05 Apr 2018, 06:35 pm

Activity

Show:

harkirat singh 10 April 2019 at 22:56

I can confirm that upgrading to 5.3.3.4 has resolved this issue for me.

Michael Offner 9 April 2019 at 15:41

added a patch to Lucee itself, so it adds serverTimeZone to all MySQL connection strings they not already have one. this is a patch that will be removed in the far future when we can assume that all users have set this.

https://github.com/lucee/Lucee/commit/32fd1b631dd4ecd8a31f151b3f72674d326755d7

Michael Offner 9 April 2019 at 14:55

we added "serverTimeZone" setting to all drivers, when you update the MySQl driver (downgrade/upgrade) and store again your datasource (that step is important) it should solve the issue.
Does it work for you?

Harry Klein 27 February 2019 at 15:17

I was too fast, the issue was not solved - saving the datasource gave me an ok. But verify an error ...
Tried this version too
https://github.com/lucee/extension-jdbc-mysql/blob/master/MySQL.cfc
without success

Harry Klein 27 February 2019 at 14:53

Had the same issue today, and solved it with this hack (thanks for mentioning it!):

<cfset fields=array( field("Server Timezone","serverTimezone","Europe/Berlin",false,""), ...
Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 2 April 2018 at 16:51
Updated 10 April 2019 at 22:56
Resolved 9 April 2019 at 16:50

Flag notifications