In my current workspace I've been refactoring the listeners in such way we don't spawn a new thread when a request comes in. I do this by using the util.concurrent features of JDK 1.5. When a listeners has to be started a new thread is started. Whenever a request comes in a thread from a thread pool is used to process the action pipeline. When doing so it is even possible for the listener to get a reference to the processing result of the last action in the pipeline very easy. Currently I'm waiting for feedback of Esteban regarding other refactorings in the listener package. As soon as I got this, I can start merging my refactorings with these of Esteban and Co's. After this merge I will try to add some unit tests for testing my changes. I also want to know what the behavior is when the listeners get a lot of load. Johan, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976265#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...