glassfish
  1. glassfish
  2. GLASSFISH-17044

[PERF] gmbal objects consuming large part of heap

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1, 3.1.1
    • Fix Version/s: None
    • Component/s: monitoring
    • Labels:
      None

      Description

      The gmbal related classes added in 3.x have contributed significantly to the heap regression usage for larger apps between 2.x and 3.x. In fact, now that other issues (notably 16747) have been fixed, these classes constitute almost all of the remaining regression. In a standard domain with specj deployed, the gmbal classes retain some 33MB of heap space (and the entire consumed heap space after startup is only 130MB).

        Issue Links

          Activity

          Hide
          Jennifer Chou added a comment -

          From Scott:

          The gmbal instances are all held by the org.glassfish.gmbal.impl.ManagedObjectManagerImpl object that is held in the ORB.

          There is a factory that produces a "null" maanged object manager impl instead of that ManagedObjectManagerImpl, so if we could arrange for the ORB to use that factory when we don't want the overhead of gmbal, that would solve the issue.

          Show
          Jennifer Chou added a comment - From Scott: The gmbal instances are all held by the org.glassfish.gmbal.impl.ManagedObjectManagerImpl object that is held in the ORB. There is a factory that produces a "null" maanged object manager impl instead of that ManagedObjectManagerImpl, so if we could arrange for the ORB to use that factory when we don't want the overhead of gmbal, that would solve the issue.
          Hide
          Jennifer Chou added a comment - - edited

          The fix should be in ORB to defer the gmbal API calls until there is a JMX client connection.

          http://java.net/jira/browse/GLASSFISH_CORBA-5

          Show
          Jennifer Chou added a comment - - edited The fix should be in ORB to defer the gmbal API calls until there is a JMX client connection. http://java.net/jira/browse/GLASSFISH_CORBA-5
          Hide
          Jennifer Chou added a comment -

          The fix should be in metro and WebServicesContainer to defer the gmbal API call until there is a JMX client connection.

          http://java.net/jira/browse/METRO-17

          Show
          Jennifer Chou added a comment - The fix should be in metro and WebServicesContainer to defer the gmbal API call until there is a JMX client connection. http://java.net/jira/browse/METRO-17
          Hide
          Jennifer Chou added a comment -

          Transfer to Scott Oaks. This is an umbrella bug to track the 2 issues in ORB and Metro.

          Show
          Jennifer Chou added a comment - Transfer to Scott Oaks. This is an umbrella bug to track the 2 issues in ORB and Metro.
          Hide
          Joe Di Pol added a comment -

          We've done all we plan on doing for 3.1.2 (See linked Metro bug). The ORB fix will have to wait for a subsequent release.

          Show
          Joe Di Pol added a comment - We've done all we plan on doing for 3.1.2 (See linked Metro bug). The ORB fix will have to wait for a subsequent release.

            People

            • Assignee:
              Scott Oaks
              Reporter:
              Scott Oaks
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: