"jokum" wrote : Hi, | | Reinitialising all the listeners even when nothing is changed in the config can't be done I think. This even means the listeners are down for the time the reinit process takes. | | In my opinion we should be able to check whether the config has changed for a certain listener. Is yes we reinitialise this listener. If not we don't do anything. | There may be good reasons why the old listener thread has to die and a new one be started that aren't just related to whether or not the config has changed. However, in general I agree: I'd like to see if we can make this configurable and not just restart them all. anonymous wrote : | Regarding the threading. Every message coming to a listener results in spawning a new thread to be usedto execute the action. We should implement a thread pool using the concurrancy features in JDK 1.5(Executors). | | I think we should have a threadpool for each listener. If so we can tune the pool per listener. Listeners/actions taking lot of time to execute can get a bigger threadpool than others. | | I think this is not that much work. | We should definitely have a pool. Maybe when you've finished the Http client/server ..? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975611#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...