Here is the probleme to solve: A webapp is registering toward a jmx service to receive a notification. How to figure out when we lost the listener? The normal behaviour of the JBossNotificationBroadcasterSupport is to cancel the listener from the list during the next notification sending is there was a network problem i.e. a tcp failure. But the web-app is not aware of that and then doesn't receive any notif any more w/o knowing. Our current temporary solution is : -first introduce a keepalive methode in the jmx service with the handback as a param, -second to overload all the methodes of JBossNotificationBroadcasterSupport that access to the registery (which is private) containing all the listener to access to a local registery instead, to be able to double check if the handback given in the keep alive param still corresponds to a listener in the registery map. If not answer false to the keepalive. Then the web-app reregister. Problem is a strong glueing w/ the current jboss version/code. Well, our problem seems pretty common and we are surprised not to be able to determine what is the standard pattern for that. Does anyone know it. Season's greetings View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000934#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...