The problem of ordering notifications can likely be solved. Another issue is whether this kind of restart-on-merge behavior should be configurable or even turned on by default. HA-JMS needs this; for other use cases having the singleton restart may be undesirable. This is particularly an issue with the HASingletonDeployer mbean, since a restart there means redeploying everything in deploy-hasingleton, a potentially lengthy process. I've no problem with adding a config flag for this, although that complicates backporting it for CP releases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030411#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...