2 Replies Latest reply on Sep 19, 2003 4:56 PM by Jeremy Crosbie

    Gauge monitor hanging with notification listeners

    Jeremy Crosbie Newbie

      I have gauge monitor running in JBoss 3.2 that is monitoring another MBean resource I created. I have a remote client that is registering itself as a notification handler for that gauge monitor, so it will receive high and low threshold alerts. I notice that when a new notification handler is registered, the JMX server creates an MBean instance in the JMX domain to manage that connection.

      When the client shuts down, the MBean remains and doesn't appear to ever go away. What's worse is that the gauge monitor appears to "freeze" in two ways. First, the monitor doesn't appear to be running as the values it reports are not consistent with the attribute it is monitoring. This leads to the second problem where notifications are not sent to new clients that register for notifications.

      A workaround seems to be that when the client shuts down we deregister all notification handlers. The gauge monitor continues functioning and new clients can connect and receive events. But this only works in the case where shutdown is normal. What I would expect is that after some time the server determines that clients are no longer available and thus silently removes them from the notification list. Is there a setting for this? Has anyone ever seen this before?