The problem, in my view, goes beyond just multithreaded listeners. It will in fact be common to all situations in which more than one listener is registered to the same [category,name,EPR], which could be quite frequent. E.g. processes in different address spaces servicing the same JMS queue. So there might not be something like "...the parent of all the threads ... responsible for registering the service..." Multithreading has been the circumstance that surfaced the problem, but in my opinion it will occur in other scenarios as well. We could consider the idea of expanding the registering key to [category,name,EPR,UID] which would solve the problem for good. Thanks. Esteban View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990784#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...