Since we’re making another run at releasing 1.0-RC42, Chris’ changes to remove the extraneous locking will make it in.
Just to be sure we haven’t introduced any concurrency problems, I’ve been running some load tests. Specifically, those described in SECTION 14 of the readme: https://github.com/apache/directory-fortress-core/blob/master/README.md A. Fortress CheckAccess: ``` mvn -Ploadtest-fortress jmeter:jmeter ``` B. Fortress CreateSession: ``` mvn -Ploadtest-fortress-createsess jmeter:jmeter ``` C. Fortress SessionPermissions: ``` mvn -Ploadtest-fortress-sessperms jmeter:jmeter ``` For example test A I am using these parameters in the jmeter file: <ThreadGroup guiclass="ThreadGroupGui" testclass="ThreadGroup" testname="Fortress CheckAccess" enabled="true"> <stringProp name="ThreadGroup.on_sample_error">continue</stringProp> <elementProp name="ThreadGroup.main_controller" elementType="LoopController" guiclass="LoopControlPanel" testclass="LoopController" testname="Loop Controller" enabled="true"> <boolProp name="LoopController.continue_forever">false</boolProp> <stringProp name="LoopController.loops">500000</stringProp> </elementProp> <stringProp name="ThreadGroup.num_threads">25</stringProp> <stringProp name="ThreadGroup.ramp_time”>1</stringProp> <boolProp name="ThreadGroup.scheduler">false</boolProp> <stringProp name="ThreadGroup.duration"></stringProp> <stringProp name="ThreadGroup.delay"></stringProp> </ThreadGroup> These tests will start 25 threads in one second. Each thread calls checkAccess 500,000 times for a total of 12.5 million iterations. So far everything looks good. Shawn
