glassfish
  1. glassfish
  2. GLASSFISH-20299

ResourceManager run level 2 slows down server initialization

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0_b84_RC1
    • Fix Version/s: 4.1
    • Component/s: performance
    • Labels:
      None

      Description

      The ResourceManager service is currently started at run level 2:

      @RunLevel( value= 2, mode=RunLevel.RUNLEVEL_MODE_NON_VALIDATING)
      @Service(name="ResourceManager") // this name is used in ApplicationLoaderService
      public class ResourceManager implements PostConstruct, PreDestroy, ConfigListener {

      Once the changes for GLASSFISH-20206 are checked in, then the initialization for ResourceManager will occur by itself while no other initialization is happening. By moving this to @InitRunLevel (level 1), then ResourceManager can be initialize at the same time as other level 1 services and (hopefully) its initialization would not slow down the startup of the server.

      This issue is for changing the run level to 1.

      It is not clear yet how much of an improvement this will make. Currently, ResourceManager takes about 120 ms to initialize.

        Issue Links

          Activity

            People

            • Assignee:
              jwells
              Reporter:
              Tom Mueller
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: