Hi Jennifer Reed,

We have completely fixed this issue and deployed at all environment . This is very specific problem hidden in user login related data.

Please find the attached analysis document for detail.

User Kick out Issue Analysis.docx

Please let me know if you need more information for the same.

Satya,Samir

Thanks
Nandkumar

Samir Satya Have we made any progress on the root causes?

Hi Nandu,

Can you please share your views on Jenn's query?

Regards,
Satya Prakash

Cc: Samir Bharti Satpute Gaurav Sodani Rakesh Roy

Satya Thanks for this update - are we saying that the root cause was both of these? Or are we trying to determine which one, and these are theories as to what may have happened?

Below are some more information on Root cause:

Root Cause:

User’s last session data/details could not be fetched from System utilization table and which forced the user to be logged out of the system

Reason 1:
In User’s table “Isactive” flag was set to 1, however, user was not logged into the system, this entry could have occurred due to an unexpected event of cluster failure or “system recycle” (workaround to reduce the system overload/utilization) resulting in “Isactive” flag was not being reset to 0

Reason 2:

2016 system utilization table data were deleted from main table (routine performed for monitoring 2017 system utilization), due to which last session ID of the active users could not be fetched and resulted in killing of all present user session

Cc: Gaurav Sodani Jennifer Reed