Jasper Reports Server Time Zone Error when Starting WebApp

0

Hi there,

I have previously installed Jasper Reports on a Linux server which was running in a BST timezone which worked fine. I am now trying to install the same version of Jasper Reports server on a linux machine which is set to UTC time.

Whenever I try to start the tomcat service I get the following error:

Caused by: org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "BST"
at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(ConnectionFactoryImpl.java:572)
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:136)
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:393)
at org.postgresql.Driver.connect(Driver.java:267)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221)
 
I have checked and the postgres database is using thre UTC timezone but for some reason the Jasper webapp seems to be stuck in BST for some reason. Any help would be appreciated.
 
hussain.miah's picture
Joined: Jul 2 2014 - 6:40am
Last seen: 6 years 2 months ago

1 Answer:

0

Shouldn't be happening if you did a fresh install of JasperReports Server and Postgres on you new server. Seems like your instance is trying to access the old PostregreSQL. Try deleting that to make sure the new instance will access the new Postgres server.

hozawa's picture
64896
Joined: Apr 24 2010 - 4:31pm
Last seen: 1 year 3 months ago
Feedback
randomness