Head in a blender

Java timezone different from OS timezone trashes Traveler

Andy Pedisich   June 13 2011 08:10:03 PM
Last week we moved a Traveler server from a Windows 2003 server to a Windows 2008 server.  Problems started right off the bat. Calendar and messages were like 3 hours off when we went for a sync with the remote devices.  Then I spotted this in the log.

06/10/2011 09:56:08 PM  Lotus Traveler: SEVERE *system The Windows OS timezone is set to GMT-300 Daylight Saving time=true while the Java Timezone is set to GMT+0 Daylight Saving time=false.  This may result in Calendar events being shifted on the traveler devices.

We had upgraded to 8.5.2 FP2 for Domino and Traveler and moved the whole thing to the Windows 2008 server, changed IP and host name.  By the way, this post is not about the move process, but rather about the error and how we fixed it.

Did a search and found this tech note.

How to check time zone related settings that could affect Lotus Notes Traveler

The big indicator was that when we did a Tell Traveler Status, we got this:

tell traveler status
06/10/2011 10:27:53 PM  Remote console command issued by Andy Pedisich/MyCompany: tell traveler status
The Lotus Notes Traveler task has been running since Fri Jun 10 22:27:37 GMT 2011.
The last successful device sync was on Fri Jun 10 22:27:51 GMT 2011.
The overall status of Lotus Notes Traveler is Green.

Note the reference to GMT.  That was the indicator that we were running Java under GMT.

We followed the tech note cook book style and restarted the Domino server a couple of times.

Had to add this to the NOTES.INI on the server:

NTS_JAVA_PARMS=-Duser.timezone=America/New_York

Finally we got this on the console:

tell traveler status
06/12/2011 10:50:01 AM  Remote console command issued by Andy Pedisich/mycompany: tell traveler status
The Lotus Notes Traveler task has been running since Fri Jun 10 22:36:24 EDT 2011.
The last successful device sync was on Sun Jun 12 10:48:39 EDT 2011.
The overall status of Lotus Notes Traveler is Green.

Note that now the time zone was EDT.  Then we did a Traveler reset of one of the admins on the call.

tell traveler reset * Ann Admin/MyCompany

She then did a manual resync of the device and sent a message which was in the right time zone.  Everything was cool.

A couple of admins got onto consoles and did the command for each of the 100+ Traveler users.  The entire process of having the issue, determining the fix, and doing it took about 4 hours.

Of course, I am so immature that all I wanted to do after we determined the fix and fixed it was to yell, "Yeah, that's right Java engine... we beat you.  In your face, Java engine!"

But I still don't know what caused the problem in the first place.

Don't you just hate that?

-Andy
Comments

08:10:03 PM June 13 2011

"Test"