1 Reply Latest reply on Feb 18, 2003 10:43 AM by raptor

    Managing multiple MBeans through an Aggregate MBean

    raptor

      The environment that I am integrating JMX into includes a SingleThreadModel servlet. I have created an MBean for the servlet at an instance level, however the aggregated information is what is desirable. For example getting or setting the timeout value across all instances of the servlets. To do this, I have an MBean that is started as a startup class that interacts with all of the instance level MBeans. For read only fields, this works fine. However, for R/W fields it creates an interesting problem.

      Using the timeout for example, if that changes, the goal is to change it across all instances which happens when the aggregate MBean interface is accessed. However, since the local instance MBeans need to be R/W to allow access for the aggregate MBean, this means that someone could easily change the timeout on a single instance, which is what I want to avoid.

      This issue would be similar when trying to manage multiple MDB's through a common MBean as well.

      Any suggestions?

        • 1. Re: Managing multiple MBeans through an Aggregate MBean
          raptor

          I found the solution to my issue using Attribute Notifications. The aggregate MBean contains the r/w properties, while the instance level MBean's offer a read only view. When changes are made on the aggregate MBean, an AttributeNotification event is fired and received by each of the instance level MBeans. If you are interested in additional details, let me know.

          Thanks.