Hi,We are experiencing an issue where email notifications which contain date fields are incorrect and is usually offset by -10 hours. For example, user enters 10/28/2014 12:00:00 AM for "Est Date" but the email notification delivers it as: Est Date: 10/27/2014 02:00:00 PM. This has just recently started happening but I'm not able to figure it out. I've edited User Profile>Time Zone to (GMT - 10:00) Pacific/Honolulu but email still sends the date wrong. Any suggestions what could be wrong? Thanks in advance!
Hi J,You might check the system times set on the db and app server, and if you have a separate notification server, check the system time on that server to see if they are set to a different time.Regards,Bill
Bill - Thanks for the suggestions but I checked the time and it looks right. What is strange, it will intermittently send the correct inputted time but majority of the email notifications will have the -10 hrs offset date. Damon - please keep me posted if you are able to resolve your issue as it seems we have the same problem.Thanks!
The JVM timezone gets shifted to GMT by either SLA or SSF (part of common services since 10.1.1.4) that is installed on the server running the Notification Server, but this is done after the DB driver initialization which causes the Notification Server to think it is getting times in GMT when it is actually not which can cause date/time issues in notification emails.
For this to be fixed both SBM needs to be 10.1.3 and above plus SOO needs to be 5.0 or above.
For earlier releases the following workaround may work.
Workaround is as follows on the server running the Notification Server:
1. stop jboss 2. go to "../Serena/SBM/Common/jboss405/bin" folder 3. open run.serena.conf.bat file 4. add following line somewhere, preferably after USER_OPTIONS: set "JAVA_OPTS=%JAVA_OPTS% -Duser.timezone=GMT" 5. save run.serena.conf.bat 6. set server (Windows) timezone to whatever you would like it to be 7. start jboss
As a further wrinkle, this only seemed to happen when a date within the next two days was selected. If it was three days or more, it looked like the notifications were OK.Anyway, I applied the fix to our app server, and it seeems to have made a difference. Will continue to monitor next week.