000031058 - Accessmanagement slow respond

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031058
Applies ToAdaptive Authentication(On-Prem) v7.x(ALL)
Platform: Any
IssueNot only logon to accessmanagement application is really slow(takes several minutes) but any operation(add/remove/edit user) is also taking so long to complete. Total number of backoffice users(RSA_BO.USERS table count) are more than 6,000.
Reviewed database log but found no issue with the database. When reviewing JVM thread dump while application awaiting respond from backend database, it seems that accessmanagment application thread does not stuck at one particular Java method, but seems calling different methods in a randomly fashion. For example:
 
threaddump\1.txt, Timestamp: 2015-06-16 10:49:15 
at com.passmarksecurity.tools.auth.dao.impl.RoleDAOImpl.getRolesForUser(RoleDAOImpl.java:58)
threaddump\2.txt, Timestamp: 2015-06-16 10:49:25
at com.passmarksecurity.tools.auth.dao.impl.OrganizationDAOImpl.getAllOrgsFromCore(OrganizationDAOImpl.java:70)
threaddump\3.txt, Timestamp: 2015-06-16 10:49:36
at com.passmarksecurity.tools.auth.dao.impl.RoleDAOImpl.getRolesForUser(RoleDAOImpl.java:58)
threaddump\4.txt, Timestamp: 2015-06-16 10:49:48
at com.passmarksecurity.tools.auth.dao.impl.OrganizationDAOImpl.getAllOrgsFromCore(OrganizationDAOImpl.java:70)
threaddump\5.txt, Timestamp: 2015-06-16 10:49:57
at com.passmarksecurity.tools.auth.dao.impl.ModuleDAOImpl.getModulesForUser(ModuleDAOImpl.java:56)
threaddump\6.txt, Timestamp: 2015-06-16 10:50:06
at com.passmarksecurity.tools.auth.dao.impl.OrganizationDAOImpl.getAllOrgsFromCore(OrganizationDAOImpl.java:70)
CauseWhen logon or performing any task, accessmanagement loads all the users from RSA_BO.USERS table and checks also user's role etc for each user. Application performance will get worse if more users are being added to the RSA_BO.USERS table.
ResolutionInstead of loading all rows, pagination will be introduced as part of the upcoming AAoP release(7.2)
WorkaroundThere is no workaround available.
NotesRefrain from adding more users to backoffice especially if number of users is more than a thousand. While this is really depend on machine specs, there is a use case of customer experiencing accesmanagement performance issue when backoffice user count is more than 6k. Please test in test environment for any implication should your system have thousands of backoffice users.

Attachments

Outcomes