Hi Heiko, "heiko.braun(a)jboss.com" wrote : a) notification failures: sure, it sound reasonable to track them through the SubscriptionManager. Resending (means queuing) would require additonal constraints (expiration policy, softening, etc). This already sounds like jms integration to me. I was thinking about that in the beginning, if further QoS capabilities can be delegated to an JMS instance. we've just created a patch to track notification failures through the SubscriptionManager mbean: http://jira.jboss.com/jira/browse/JBWS-1406 bye Alessio Soldano http://www.javalinux.it/blogs/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990126#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...