Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67534

JMX doesn't work correctly after restarting instance

XMLWordPrintable

      Summary

      JMX doesn't work correctly after restarting instance.

      Steps to Reproduce

      1. Enable JMX monitoring with following a page "Live monitoring using the JMX interface"
      2. Restart Jira
      3. Access the JMX port via JConsole

      Expected Results

      All the metrics described in the above page should be available in JConsole UI.

      Actual Results

      Only a metric BasicDataSource (under com.atlassian.jira) are available.

      Notes

      This problem has already been fixed on Jira 7.10.1.

      Workaround

      Please reenable JMX monitoring from   > System > JMX monitoring.

            [JRASERVER-67534] JMX doesn't work correctly after restarting instance

            set-jac-bot made changes -
            Fixed in Enterprise Release/s New: [Download 7.6|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html]
            Bugfix Automation Bot made changes -
            Minimum Version New: 7.06
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2831537 ] New: JAC Bug Workflow v3 [ 2922763 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2706946 ] New: JAC Bug Workflow v2 [ 2831537 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Yuki Okamoto (Inactive) made changes -
            Fix Version/s New: 7.6.6 [ 79690 ]
            Fix Version/s New: 7.8.2 [ 78393 ]
            Fix Version/s Original: 7.10.1 [ 79903 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue duplicates JRASERVER-66802 [ JRASERVER-66802 ]
            Yuki Okamoto (Inactive) made changes -
            Description Original: h3. Summary


            h3. Environment
            *
            *

            h3. Steps to Reproduce
            #Step 1
            #Step 2

            h3. Expected Results

            h3. Actual Results
            The below exception is thrown in the xxxxxxx.log file:
            {noformat}
            ...
            {noformat}
             
            h3. Notes

            h3.Workaround
            		New: h3. Summary

            JMX doesn't work correctly after restarting instance.
            h3. Steps to Reproduce
             # Enable JMX monitoring with following a page ["Live monitoring using the JMX interface"|https://confluence.atlassian.com/adminjiraserver/live-monitoring-using-the-jmx-interface-939707304.html]
             # Restart Jira
             # Access the JMX port via [JConsole|https://docs.oracle.com/javase/8/docs/technotes/guides/management/jconsole.html]

            h3. Expected Results

            All the metrics described in [the above page|https://confluence.atlassian.com/adminjiraserver/live-monitoring-using-the-jmx-interface-939707304.html] should be available in JConsole UI.
            h3. Actual Results

            Only a metric {{BasicDataSource}} (under {{com.atlassian.jira}}) are available.
            h3. Notes

            This problem has already been fixed on Jira 7.10.1.

            h3. Workaround

            Please reenable JMX monitoring from  !https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png|width=18! _> System > JMX monitoring_.
            Yuki Okamoto (Inactive) made changes -
            Description New: h3. Summary


            h3. Environment
            *
            *

            h3. Steps to Reproduce
            #Step 1
            #Step 2

            h3. Expected Results

            h3. Actual Results
            The below exception is thrown in the xxxxxxx.log file:
            {noformat}
            ...
            {noformat}
             
            h3. Notes

            h3.Workaround
            Yuki Okamoto (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

              Unassigned Unassigned
              yokamoto Yuki Okamoto (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: