2 Replies Latest reply on May 24, 2005 11:06 AM by dimitris

    where do all mbean attributes come from. Not all are defined

      I am trying to understand where all attributes displayed on JMX console for a given MBean are sourced (come from). I am running the JBoss default server and am looking at the jboss-service.xml file in the default server's conf directory. The attributes explicity defined in an MBean such as:

      <!-- A Thread pool service -->

      JBoss System Threads
      System Threads
      <!-- How long a thread will live without any tasks in MS -->
      60000
      <!-- The max number of threads in the pool -->
      10
      <!-- The max number of tasks before the queue is full -->
      1000
      run


      only identify 6 of the 10 that are displayed by the JMX console (below)

      PoolNumber .
      Instance
      KeepAliveTime
      QueueSize
      BlockingMode
      ThreadGroupName
      Name
      MaximumQueueSize
      MinimumPoolSize
      MaximumPoolSize


      THe question is Where do the other 4 come from? WHere are they defined?

      THank you in advance for the answer,

      - andy

        • 1. Re: where do all mbean attributes come from. Not all are def

          please disregard and see the next post. thank you

          • 2. Re: where do all mbean attributes come from. Not all are def
            dimitris

            In the jboss-service.xml descriptors we simply inject values to any number of setable attributes, we don't declare the attributes there.

            If we are talking about standard mbeans, attributes are derived from the MBean interface implemented by the class (using reflection), by those methods that follow the java bean pattern:

            public <some-type> getAttrName();
            public void setAttrName(<some-type>);

            (read the jmx spec).

            In jboss we also have xmbean (when an xmbean descriptor is provided, where we can explicitly specify the attributes there).

            See for example the descriptors in server/default/conf/xmdesc directory.