Customer is at +9:00 timezone. The alarm reported 9 hours later than local time
1、 The alarm time in eSight is 9 hours later than
local time in South Korea, and the time of the physical server is normal. By
input the query command“eview.globalTimezoneOffse” on the browser console, we make sure that the JRE time in eSight get is UTC+0,which
is the reason of the issue.
2、 By analyzing the log of eSight，we
found the JRE time in eSight is alright before 8:49 local time in Korea in
November 25th, after this
time, the issue appeared.
3、 By analyzing the code of eSight, we confirm that
there is a sight which will set the JRE time zone to UTC+0 when using the Automatic
Discovery Devices feature. After further confirmation, there are 19 tasks in
the business eSight. And there are 3 Automatic Discovery Devices tasks
executing at 8:49 local time in Korea in November 25th , which anastomose
the time issue appeared.
4、 We set up a laboratory environment, and reproduce
the problem in the same scene. With this, we make sure that the Automatic
Discovery Devices Mission cause the JRE time zone to UTC+0.
5、 As the further
analysis , multiple threads tasks will
set the time zone to UTC+0. But if the task executes at the different time , the issue wouldn’t appear.
1.Time zone in eSight is UTC+0 now， we need to cancel all the Automatic Discovery Devices Mission which execute at the same time, and then restart eSight. After this, the data in eSight will be all right.
2.Don’t recreate the Automatic Discovery Devices Mission which execute at the same time in eSight.