With my effort to move the configuration/setup of the security managers out of JaasSecurityManagerService, the security managers created may not be set up with a cachepolicy.
I need to check this.
Deployment/Undeployment of the test archive "security-spec.jar" is taking around 20sec.
I profiled JBAS and made some changes to reduce JNDI lookups of the security managers... This probably cut the overall time by some percentage (maybe 40%). I still see that remoting (and Arjuna) taking up cpu cycles during the profile......
Scott, what is the latest execution time for the test case on your box?
This is on a different box.
with the current 2 threads, 10 iterations:
[junit] Tests run: 25, Failures: 0, Errors: 4, Time elapsed: 29.894 sec
Using 1 thread, 50 iters as shown in the other run its:
[junit] Tests run: 25, Failures: 0, Errors: 4, Time elapsed: 41.767 sec
which I would guess would be around 25s on the server box I showed earlier.
I won't be able to check that until Thu as I'm traveling.
The current server box time is down to 31 secs.
[junit] Running org.jboss.test.security.test.EJBSpecUnitTestCase
[junit] Tests run: 25, Failures: 0, Errors: 4, Time elapsed: 31.608 sec