The target MBeanServer of a CascadingServiceMBean is usually the MBeanServer in which that CascadingServiceMBean is registered. It is recommended to instantiate at most one CascadingServiceMBean per target MBeanServer. If no ObjectName is specified when registering the CascadingServiceMBean, then the CascadingServiceMBean will supply its own default name: {@link #CASCADING_SERVICE_DEFAULT_NAME CASCADING_SERVICE_DEFAULT_NAME}=new ObjectName("com.sun.jdmk:type=CascadingService").
If the JMX Connection with a source MBeanServer fails or is permanently closed, the CascadingServiceMBean will emit a {@link JMXConnectionNotification} with the following parameters:
If the cascading is unmounted ( {@link #unmount unmount} was called) thenthe CascadingServiceMBean will emit a {@link JMXConnectionNotification} with the following parameters:
Note: In this implementation, the {@link #mount mount} operation does not perform any checks with regards to the coherency of the supplied targetPath. It is under the responsibility of the application to conform to the rules documented in {@link com.sun.jdmk.remote.cascading#The_File_System_Analogy The File System Analogy}
In this implementation, the CascadingService relies on the {@link ProxyCascadingAgent}. @since Java DMK 5.1
|
|
|
|
|
|