glassfish
  1. glassfish
  2. GLASSFISH-9801

Monitoring: Type attribute required for v3 runtime components

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: future release
    • Component/s: ejb_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      In case of v3 runtime tree, there is no way to distinguish between different
      components such as modules, beans. We need to provide type attributes for nodes
      representing such components. Here is the list of components, the nodes of which
      requires type attribute-

      Module Node
      Type:
      Ejb Module
      Standalone Ejb Module
      Web Module
      Standalone Web Module

      Bean Node
      Type:
      Stateful Session Bean
      Stateless Session Bean
      Entity Bean
      Message Driven Bean

        Activity

        Hide
        rajeshwar added a comment -
            • Issue 8837 has been marked as a duplicate of this issue. ***
        Show
        rajeshwar added a comment - Issue 8837 has been marked as a duplicate of this issue. ***
        Hide
        abbagani added a comment -

        We will need the type attribute at the ejb module level and also at the bean
        level. Transferring the bug to Marina.

        Show
        abbagani added a comment - We will need the type attribute at the ejb module level and also at the bean level. Transferring the bug to Marina.
        Hide
        Nazrul added a comment -

        ...

        Show
        Nazrul added a comment - ...
        Hide
        marina vatkina added a comment -

        Need an API to use, but I can only set the bean node type, not the module type.

        Show
        marina vatkina added a comment - Need an API to use, but I can only set the bean node type, not the module type.
        Hide
        abbagani added a comment -

        We will need the type attribute under ejb-module and bean level.

        Module level
        ============
        ear

        RosterApp/RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague

        We will need to define a new StatsProvider with just one attribute
        (module-type). You could do this as an inner class (Would it be in
        MonitoringRegistryMediator?). In the above case, we will need this attribute
        under 'RosterAppEjb\.jar'. The type would say, if it is a 'standalone ejb' or an
        'ejb'. Pick the constants that Deployment or ejb-container might already be using.

        standalone module (jar)
        ------------------------------

        RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague

        Same as in ear. Need a type attribute under 'RosterAppEjb\.jar'

        Bean level
        ========

        RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague

        We will need an attribute called type (bean-type). This should be easy, since
        you already have a StatsProvider for a bean which has some existing attributes.
        The bean-type should say what type of bean it is.

        I think it should be in EJBStatsProvider (define type as new attribute and set
        the type value when you are instantiating one of the derived classes).

        Show
        abbagani added a comment - We will need the type attribute under ejb-module and bean level. Module level ============ ear — RosterApp/RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague We will need to define a new StatsProvider with just one attribute (module-type). You could do this as an inner class (Would it be in MonitoringRegistryMediator?). In the above case, we will need this attribute under 'RosterAppEjb\.jar'. The type would say, if it is a 'standalone ejb' or an 'ejb'. Pick the constants that Deployment or ejb-container might already be using. standalone module (jar) ------------------------------ RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague Same as in ear. Need a type attribute under 'RosterAppEjb\.jar' Bean level ======== RosterAppEJB\.jar/LeagueEJB/bean-methods/getCitiesOfThisLeague We will need an attribute called type (bean-type). This should be easy, since you already have a StatsProvider for a bean which has some existing attributes. The bean-type should say what type of bean it is. I think it should be in EJBStatsProvider (define type as new attribute and set the type value when you are instantiating one of the derived classes).
        Hide
        marina vatkina added a comment -

        monitoring is p3

        Show
        marina vatkina added a comment - monitoring is p3
        Hide
        marina vatkina added a comment -

        -> 3.1

        Show
        marina vatkina added a comment - -> 3.1

          People

          • Assignee:
            marina vatkina
            Reporter:
            rajeshwar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: