I'm tempted to have a standalone module manage the named semaphores (perhaps called SemaphoreManager). The SemaphoreManager api methods could be used for reconfiguration (JMX aspect could expose them in the JMX console.) The api should allow: * List all named semaphores (show name, total permit count + current available permits) * Increase number of permits for a named semaphore * Decrease number of permits for a named semaphore I'm still trying to understand how all of this AOP stuff works together. I see that the SemaphoreAspect is loosely coupled with the underlying semaphore instance via the SemaphoredObject class. Should we have a SemaphoreFactory class that can return a SemaphoredObject implementation that is based on a named semaphore? I suppose that the SemaphoreFactory could also return a SemaphoredObject based on an anonymous semaphore as well. The SemaphoreFactory factory would depend on the SemaphoreManager for resolving the semaphore instances. Make any sense? On a different node, I can build trunk with "mvn install" command. I would like to run the testsuite but "mvn test" doesn't seem to do much. How can I run the unit tests? Scott View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103271#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...