On 5/31/2014 11:47 PM, John R Pierce wrote:
On 5/31/2014 11:41 PM, David Wall wrote:
FATAL: invalid value for parameter "TimeZone": "PST"
I'd be using "America/Los_Angeles" as the timezone rather than PST,
as the TLA timezones are ambiguous (CST is both Central Standard Time
in the USA, and China Standard Time).
but thats probably not the problem, hard to guess what is, sounds
like you have a lot going on.
PG itself has the timezone US/Pacific set in postgresql.conf
In Linux, we show:
lrwxrwxrwx 1 root root 39 Apr 23 16:00 /etc/localtime ->
/usr/share/zoneinfo/America/Los_Angeles
Even when we use PST in our Java code, we use PST8PDT.
The exception occurs when JDBC tries to connect to PG:
2014-05-31 22:14:34,351 ERROR (eSignForms) SQLException:
ConnectionPool.makeConnection(esf) to URL:
jdbc:postgresql://localhost.localdomain:25432/zingr:
2014-05-31 22:14:34,352 ERROR (eSignForms) Message: FATAL: invalid
value for parameter "TimeZone": "PST"
org.postgresql.util.PSQLException: FATAL: invalid value for parameter
"TimeZone": "PST"
at
org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:574)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:177)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:138)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:29)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:21)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:31)
at
org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:410)
at org.postgresql.Driver.connect(Driver.java:280)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at
com.esignforms.db.ConnectionPool.makeConnection(ConnectionPool.java:302)
And of course none seems to explain why it works often enough, but then
fails as more apps are deployed. Ugh!
