Inside the cluster, you can add a listener to a MBean on a remote element. All notifications are processed asynchronously by default. You can bypass this default asynchronous processing if the notification implements com.sap.engine.services.jmx.server.SynchronousNotification.
If you are interested in MBeanServerNotifications, that is, the (un)registration of MBeans, you must add a notification listener to the MBeanServerDelegate. Since the MBeanServer delegate is a clustered MBean, the listener will be added to the local instance of the delegate. You will, however, receive a notification if a MBean that is visible from the listener’s element is (un)registered on a remote element.
Adding a listener for MBeanServerNotifications causes the MBeanServer to send a broadcast message for each MBean that is (un)registered. That is, avoid it whenever possible and do not forget to unregister the listener if you no longer require notification.