[Deploying Sakai] Time zone mismatch on sakai 2.8
Raad Al-Rawi
Raad.Al-Rawi at admin.cam.ac.uk
Tue Nov 29 07:59:15 PST 2011
Yes, this is what you need to do to anchor the time zone, we put a couple more options on JAVA_OPTS to help with localisation:
-Duser.timezone=Europe/London -Duser.language=en -Duser.region=GB
Cheers
Raad
From: production-bounces at collab.sakaiproject.org [mailto:production-bounces at collab.sakaiproject.org] On Behalf Of Mike De Simone
Sent: 29 November 2011 15:43
To: Matthew Jones
Cc: production at collab.sakaiproject.org; Eduardo
Subject: Re: [Deploying Sakai] Time zone mismatch on sakai 2.8
This might be an oracle thing. I just checked MySQL that's running Sakai 2.8 and events & session times are in the local time rather than GMT. I do actively set the timezone as a java system property, so maybe that overrides something?
e.g., in setenv.sh: JAVA_OPTS="$JAVA_OPTS -Duser.timezone=US/Pacific"
Thanks,
-------------------------------
Mike DeSimone
Lead Systems Engineer
rSmart | 602-490-0473
On Tue, Nov 29, 2011 at 08:37, Matthew Jones <jonespm at umich.edu<mailto:jonespm at umich.edu>> wrote:
FYI: Sakai Events (and other fields that store the date/time like session) are stored in GMT. This is because it will be the only time that is ever constant. It's possibly your data center could relocate, you could have daylight savings time. GMT never changes with seasons and is always a constant.
Here's some additional information from a post a few years ago.
http://collab.sakaiproject.org/pipermail/sakai-dev/2009-September/003731.html
-Matthew
On Tue, Nov 29, 2011 at 8:46 AM, Eduardo <eduzav at hotmail.com<mailto:eduzav at hotmail.com>> wrote:
Hy, we're using Sakai 2.8 on Argentina and we have difference time between application and database ( three hours mismatch)
Example: when a user logs on application at 17hs the sesión_start field on table is 20hs
The time zone of Argentina is GMT -3.
All servers (backend and frontends) are synchronizing the hour using ntp protocol (ar.pool.ntp.org<http://www.pool.ntp.org/zone/ar>) and the time zone configurated is GMT+3 (the operating systems are OEL 5.5)
On backend we're using Oracle 10g release 4 and the time configurated on instance is OK.
select systimestamp from dual;
29/11/2011 10:32:06,241764 AM -03:00
select current_timestamp from dual;
29/11/2011 10:29:39,827614 AM -03:00
The time on application layout is Ok but the time on oracle table is incorrect.
The table we're monitoring is sakai.session and the fields are SESSION_START and SESSION_END.
On the other hand catalina evironment is:
CATALINA_OPTS='-server -Xms512m -Xmx3072m -XX:PermSize=128m -XX:MaxPermSize=512m -XX:NewSize=192m -XX:MaxNewSize=384m -Djava.awt.headless=true -Dhttp.agent=Sakai -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false -Dsun.lang.ClassLoader.allowArraySyntax=true -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=33331 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Duser.language=es -Duser.region=ES'
I don't know how can I fix that error, what do you suggest me?
Thanks,
Eduardo Zavala
_______________________________________________
production mailing list
production at collab.sakaiproject.org<mailto:production at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/production
TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org<mailto:production-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
_______________________________________________
production mailing list
production at collab.sakaiproject.org<mailto:production at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/production
TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org<mailto:production-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20111129/4d4b07e6/attachment-0001.html
More information about the production
mailing list