glassfish
  1. glassfish
  2. GLASSFISH-4320

[v3] Expose Grizzly's Resource Consomption Management API, support officialy RCM

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: not determined
    • Component/s: other
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      4,320
    • Status Whiteboard:
      Hide

      v3-prd-item gfv3-prelude-excluded

      Show
      v3-prd-item gfv3-prelude-excluded

      Description

      Resource Consomption Management is implemented since v2 but not officially
      supported:

      http://blogs.sun.com/sduv/entry/resource_management_in_enterprise_application
      http://weblogs.java.net/blog/jfarcand/archive/2007/06/improving_ajax_1.html

      Now that Grizzly is fronting every thing in v3, RCM can be extended to support
      GIOP/Corba, JMS, etc.

        Issue Links

          Activity

          Hide
          jfarcand added a comment -

          ...

          Show
          jfarcand added a comment - ...
          Hide
          jfarcand added a comment -
              • Issue 4384 has been marked as a duplicate of this issue. ***
          Show
          jfarcand added a comment - Issue 4384 has been marked as a duplicate of this issue. ***
          Hide
          Sivakumar Thyagarajan added a comment -

          Grizzly's RCM can be viewed as just another instance of the request
          prioritization planned in the container ( issue 4147 ) and so I think exposing
          Grizzly' RCM separately in the admin GUI wouldn't be right.

          This would essentially mean a user would need to use Grizzly RCM for Grizzly and
          a "unified" resource prioritization model for all the other resources/containers
          in v3, which doesn't seem right.

          Show
          Sivakumar Thyagarajan added a comment - Grizzly's RCM can be viewed as just another instance of the request prioritization planned in the container ( issue 4147 ) and so I think exposing Grizzly' RCM separately in the admin GUI wouldn't be right. This would essentially mean a user would need to use Grizzly RCM for Grizzly and a "unified" resource prioritization model for all the other resources/containers in v3, which doesn't seem right.
          Hide
          jfarcand added a comment -

          Siva, since we are planning to use port unification, every connection will be
          analyzed inside Grizzly via its tcp listener. So RCM should happens there since
          the thread pool is handled by Grizzly. So I'm not sure I see that as 'just an
          instance'. I agree with you if the case of not using port unification.

          For sure we need to continue supporting what we have in v2 and add configuration
          support under the new grizzly-config element.

          Let's try to have a meeting with Jerome/Ken on that (just reply on the email
          I've sent you internally )

          Show
          jfarcand added a comment - Siva, since we are planning to use port unification, every connection will be analyzed inside Grizzly via its tcp listener. So RCM should happens there since the thread pool is handled by Grizzly. So I'm not sure I see that as 'just an instance'. I agree with you if the case of not using port unification. For sure we need to continue supporting what we have in v2 and add configuration support under the new grizzly-config element. Let's try to have a meeting with Jerome/Ken on that (just reply on the email I've sent you internally )
          Hide
          jfarcand added a comment -

          Currently available by adding, in domain.xml:

          <property name="enableRCM" value="true"/>

          Show
          jfarcand added a comment - Currently available by adding, in domain.xml: <property name="enableRCM" value="true"/>
          Hide
          kumara added a comment -

          Add gfv3-prelude-include to status whiteboard

          Show
          kumara added a comment - Add gfv3-prelude-include to status whiteboard
          Hide
          kumara added a comment -

          v3 defect tracking

          Show
          kumara added a comment - v3 defect tracking
          Hide
          kumara added a comment -

          The initial implementation is done. We need to go through formal
          specification/documentation process and then adapt to that for final release.

          Show
          kumara added a comment - The initial implementation is done. We need to go through formal specification/documentation process and then adapt to that for final release.
          Hide
          jfarcand added a comment -

          Re-assign to Siva and Sahoo will drive the effort for the overall GlassFish, not
          only web container.

          Show
          jfarcand added a comment - Re-assign to Siva and Sahoo will drive the effort for the overall GlassFish, not only web container.
          Hide
          kumara added a comment -

          Defect->Feature

          Show
          kumara added a comment - Defect->Feature
          Hide
          Tom Mueller added a comment -

          Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          Show
          Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

            People

            • Assignee:
              Sivakumar Thyagarajan
              Reporter:
              jfarcand
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: