Can you show the trace to: org.jboss.security.plugins.JaasSecurityManager.isValid()
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock wrote:
On Wed, 2003-09-10 at 13:43, Scott M Stark wrote:
Yes, its going to depend on what the resource adaptor wants for its security info and the pool is most likely going to have to get the comparator from the ra configuration. We can start with a default comparator that is based on the javax.resource.spi.security.PasswordCredential.
My previous jboss-dev post hasn't show up (yet?). Basically, I can't see a way of bypassing Set/Iterator work that would make the direct use of PasswordCredential significantly faster.
Re-analysising the data, I found another big point of contention. It is on the method: org.jboss.security.plugins.JaasSecurityManager.isValid() The securityDomain is globally locked for the cache/authentication subject construction.From a profiler run this looks a lot more significant thanthe others I previously identified.
Regards, Adrian
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
