- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    6
- 
        b55
- 
        generic
- 
        generic
                    In a JMX client I create an MBean with ObjectName ":type=Simple".
The Simple MBean emits notifications when one of its attributes
changes.
The client registers a listener on the Simple MBean. The call to
addNotificationListener returns successfully either when calling
it through MBeanServerConnection.addNotificationListener or through
a Simple MBean proxy.
Then I set one of the Simple MBean attributes and I can see in the
server traces that the notification is emitted but it is never
received on the client side.
The same scenario on the server side works fine so I guess the bug
comes from the way the connector server filters the notifications
before sending them to the client side.
###@###.### 2005-03-10 10:48:38 GMT
            
The Simple MBean emits notifications when one of its attributes
changes.
The client registers a listener on the Simple MBean. The call to
addNotificationListener returns successfully either when calling
it through MBeanServerConnection.addNotificationListener or through
a Simple MBean proxy.
Then I set one of the Simple MBean attributes and I can see in the
server traces that the notification is emitted but it is never
received on the client side.
The same scenario on the server side works fine so I guess the bug
comes from the way the connector server filters the notifications
before sending them to the client side.
###@###.### 2005-03-10 10:48:38 GMT
- relates to
- 
                    JDK-8343838 Test EmptyDomainNotificationTest.java fails with ListenerNotFoundException -           
- Resolved
 
-