"alesj" wrote : | What I would like to do, is to test that a single deploy|undeploy and (add|remove)+process don't corrupt each other in multithread requests. | Another test would include a shutdown thread, from where on all other non-shutdown (deploy|undeploy) threads should fail. | The question is how to gather required information, meaning that a thread was legally allowed to go (or not go) past the locks that we've put? | Done. The first test - DeployerSingleDeploymentTestCase.testMultiThreads - is more a proof of concept through design, unleashing multiple threads just additionally confirms assumptions that deploy/undeploy and (add|remove)+process don't interfere with each other. :-) The second one - DeployerSingleDeploymentTestCase.testMultiThreadsAndShutdown - is better. :-) I'm checking if certain DeployerClient method invocation got past the read lock, as such not being valid to fail due to shutdown. All others that didn't get past the read lock must fail. Perhaps only the way how I'm checking if thread got past the lock is a bit too impl detail - intercepting Deployment.getName method invocation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106680#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...