Tom Fonteyne created SECURITY-664: ------------------------------------- Summary: jndi lookups for a security domain should be cached Key: SECURITY-664 URL: https://issues.jboss.org/browse/SECURITY-664 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.4.SP8 Reporter: Tom Fonteyne Assignee: Anil Saldhana In certain scenarios, there are many JNDI lookups being done, which are taking up to 10-20% of performance. org/​ jboss/​ security/​ plugins/​ DefaultSecurityManagement.java Should instead of creating new instances all the time be changed to cache per security domain. Quote from the customer: ------------------------ The getter methods in the default security management have a factory method character. The instances change after creation (actually) no more, because security domain does not change in context. Therefore, I think it is better if the instances AuditManager, AuthenticationManager, AuthorizationManager, IdentityManager, TrustManager and MappingManager are stored in the JBossSecurityContext instance itself. Also in the same time the jndi lookup java:/policyRegistration is performed. I have not found the code location where the lookup is performed. But this source code should also be changed. ------------------------ The customer did quite some investigation, there are more details in the case notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira