Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-21175

Total memory inside the System information page is taking the Initial memory pool size set for the Java properties

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 9.6.0
    • 7.1.4, 7.2.1
    • Windows
    • None

      Issue Summary

      The Total memory report inside the Bamboo admin > Overview > System > System information page is reporting the value set for the "Initial memory pool" inside the Java properties instead of the "Maximum memory pool".

      Steps to Reproduce

      You must have Bamboo running as a Windows Service.

      1. Follow the steps inside this page to update the Java properties.
      2. Go to the Java tab.
      3. Increase the Maximum memory pool from 1024 to 2048.
      4. Restart the Service.
      5. Access Bamboo from the UI and go to the Bamboo admin > Overview > System > System information page.
      6. Find the Total memory report.

      Expected Results

      Total memory will report 2048 MB since we increased the Maximum memory pool.

      Actual Results

      Total memory will continue to report whatever number you have for the Initial memory pool. That number will only change if you change the Initial memory pool.

      Notes

      This is not affecting the ability of the JVM to use the amount of memory set for the Maximum memory pool. It only seems to be affecting reporting inside the System information page.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

          Form Name

            [BAM-21175] Total memory inside the System information page is taking the Initial memory pool size set for the Java properties

            Alexey Chystoprudov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Eduardo Alvarenga (Inactive) made changes -
            Fix Version/s New: 9.6.0 [ 106907 ]
            Eduardo Alvarenga (Inactive) made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Eduardo Alvarenga (Inactive) made changes -
            Status Original: Gathering Impact [ 12072 ] New: In Progress [ 3 ]
            Eduardo Alvarenga (Inactive) made changes -
            Remote Link New: This issue links to "+core+ Dogfooding › Test Git Branch Detection › issue-BAM-21175_add_maxMemory_to_SystemInfo_on_both_Server_and_Agents_panels (tardigrade-bamboo)" [ 872947 ]
            Eduardo Alvarenga (Inactive) made changes -
            Assignee New: Eduardo Alvarenga [ 73868399605e ]
            Zuzanna Struczewska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 599803 ]
            Jan Majkutewicz (Inactive) made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Bruno Rosa made changes -
            Description Original: h3. Issue Summary

            The *Total memory* report inside the *Bamboo admin > Overview > System > System information* page is reporting the value set for the _"Initial memory pool"_ inside the Java properties instead of the _"Maximum memory pool"_.

            h3. Steps to Reproduce
            {panel:title=|borderStyle=dashed|borderColor=#6a8eb3|titleBGColor=#f8f8f8|bgColor=#f8f8f8}
            You must have Bamboo running as a Windows Service.
            {panel}
            # Follow the steps inside [this page|https://confluence.atlassian.com/bamboo/configuring-your-system-properties-289277345.html] to open the Bamboo Windows Service properties.
            # Go to the *Java* tab.
            # Increase the Maximum memory pool from 1024 to *2048*.
            # Restart the Service.
            # Access Bamboo from the UI and go to the *Bamboo admin > Overview > System > System information* page.
            # Find the *Total memory* report.

            h3. Expected Results

            *Total memory* will report 2048 MB since we increased the Maximum memory pool.

            h3. Actual Results

            *Total memory* will continue to report whatever number you have for the Initial memory pool. That number will only change if you change the Initial memory pool.

            h3. Notes

            This is not affecting the ability of the JVM to use the amount of memory set for the Maximum memory pool. It only seems to be affecting reporting inside the System information page.

            h3. Workaround

             Currently there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            The *Total memory* report inside the *Bamboo admin > Overview > System > System information* page is reporting the value set for the _"Initial memory pool"_ inside the Java properties instead of the _"Maximum memory pool"_.

            h3. Steps to Reproduce
            {panel:title=|borderStyle=dashed|borderColor=#6a8eb3|titleBGColor=#f8f8f8|bgColor=#f8f8f8}
            You must have Bamboo running as a Windows Service.
            {panel}
            # Follow the steps inside [this page|https://confluence.atlassian.com/bamboo/configuring-your-system-properties-289277345.html] to update the Java properties.
            # Go to the *Java* tab.
            # Increase the Maximum memory pool from 1024 to *2048*.
            # Restart the Service.
            # Access Bamboo from the UI and go to the *Bamboo admin > Overview > System > System information* page.
            # Find the *Total memory* report.

            h3. Expected Results

            *Total memory* will report 2048 MB since we increased the Maximum memory pool.

            h3. Actual Results

            *Total memory* will continue to report whatever number you have for the Initial memory pool. That number will only change if you change the Initial memory pool.

            h3. Notes

            This is not affecting the ability of the JVM to use the amount of memory set for the Maximum memory pool. It only seems to be affecting reporting inside the System information page.

            h3. Workaround

             Currently there is no known workaround for this behavior. A workaround will be added here when available

              73868399605e Eduardo Alvarenga (Inactive)
              brosa Bruno Rosa
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: