I recently updated to the latest version of OPENNMS (1.11.0), and now all the times in the outages table are out by 20 hours.
The events are recorded in PostgreSQL with the correct time (i.e. they are contained in a field named eventtime timestamp with time zone and are
recorded with +10 timezone after the time). For example when I perform a scan right now 28/6/2012 at 10:23 am in Sydney, the event on my console
shows 28/06/12 00:22:52, while PostgresSQL records the event as 2012-06-28 10:22:52.143+10 in a field named eventtime timestamp with timezone.

When I run tzutil /g on the server at a dos prompt, my time zone displays as "AUS Eastern Standard Time" which is UTC+10:00, however as you can see
below, OPENNMS picks up the server time as EST 2012 hence th 20 hours difference.

The details of my installation are as follows:

Version: 1.11.0
Server Time: Wed Jul 11 13:46:00 EST 2012
Client Time: Wed Jul 11 13:46:02 UTC+1000 2012
Java Version: 1.7.0_05 Oracle Corporation
Java Virtual Machine: 23.1-b03 Oracle Corporation
Operating System: Windows Server 2008 R2 6.1 (amd64)
Servlet Container: jetty/7.5.4.v20111024 (Servlet Spec 2.5)
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64;
Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; MDDR; InfoPath.3)
Database Type: PostgreSQL
Database Version: 9.1.4

*
I have found a post for the same problem which relates to a linux
installation which I have pasted a link to below. If anybody has any ideas
as to what I need to do for a Windows installation, it would be
appreciated.*

http://opennms.530661.n2.nabble.com/Problems-with-timestamp-conversion-td7458405.html
http://opennms.530661.n2.nabble.com/Problems-with-timestamp-conversion-td7458405.html

–