Re: Error when setting useTimezone=true

[Paul Darling]

I overlooked some log4j data that provides the stackof the original problem, that lead to the ExceptionInInitializeError:-

2005-08-22 05:25:32,394 ERROR [TP-Processor3] com.tumbleweed.mg.database.DBPropertyMap - DB Connection problem or Error executing query: "SELECT name,value FROM local_settings"
java.sql.SQLException: The server timezone value 'PDT' represents more than one timezone. You must configure either the server or client to use a more specifc timezone value if you want to enable timezone support. The timezones that 'PDTmaps to are: America/Los_Angeles, America/Juneau, America/Boise, America/Vancouver, America/Dawson_Creek, America/Inuvik, America/Whitehorse, America/Dawson, America/Tijuana
at com.mysql.jdbc.Connection.configureTimezone(Connection.java:3127)
at com.mysql.jdbc.Connection.initializePropsFromServer(Connection.java:3252)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:1780)
at com.mysql.jdbc.Connection.<init>(Connection.java:430)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:268)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:46)

So the problem appears to be that PDT is the configured MySQL timezone and the driver cannot use this as it's ambiguous.

The solution therefore seems to be to ensure that the timezone is initialized (and reset using only) an unambiguous timezone. Is this correct? Is this a common problem, as I would expect PDT (and similar) to be a commonly configured timezone.

Paul