When Setting Vacation, Values Of vacationStartDate and vacationEndDate are Wrong
Last updated on JANUARY 11, 2018
Applies to:Oracle Communications Convergence - Version 1.0 and later
Information in this document applies to any platform.
When configuring vacation settings in Convergence, the values of the ldap attributes vacationStartDate and vacationEndDate are an additional x hours off from the expected date and time.
Eg. consider the following setup : Convergence 1 patch 17, operating completely in the Japanese time zone. The Japanese time zone is (currently) GMT+9.
user.common.timezone = Asia/Tokyo
user.common.enablesmartTZ = true
Convergence Server platform timezone (eg. Solaris)
# grep '^TZ' /etc/TIMEZONE
The end-user's browser runs on a system having Asia/Tokyo as time zone.
Steps taken :
- Log in to Convergence
- Options -> Mail -> Local Account -> Vacation Message
- Set the following Vacation Duration and Save :
- Perform an ldapsearch :
20120202060000Z corresponds to 2012 02 02 15:00 JST !
20120204055900Z corresponds to 2012 02 04 14:59 JST !
The expected vacationStartDate would be 20120202150000Z.
Meaning, the saved value is an additional 9 hours off from the expected date and time! As a result, in this case, vacation messages will start to be sent too soon and ending too soon.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms