Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8043323

reopen JDK-8021038 : No CPULoad-events when recording a GlassFish instance

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 7u45
    • Fix Version/s: None
    • Component/s: hotspot
    • Subcomponent:
      svc
    • OS:
      windows_7

      Description

      FULL PRODUCT VERSION :
      java version "1.7.0_45"
      Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
      Java HotSpot(TM) Client VM (build 24.45-b08, mixed mode, sharing)

      FULL OS VERSION :
      Microsoft Windows [Version 6.1.7601]

      A DESCRIPTION OF THE PROBLEM :
      I came across the bug JDK-8019921, but this and the backport bug JDK-8021038 are stated as fixed and update 45 got released some days ago.

      http://stackoverflow.com/questions/19559992/no-cpu-usage-recorded-in-java-mission-control-flight-recorder

      THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try

      THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Simply use FlightRecorder with any Java application on Windows 7 64 Bit with JRE 7u45, options don't matter.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      I would epxect that CPULoad is available in FlightRecorder, as it is in JMX Console. But it is not in FlightRecorder, instead following trace info is logged: Unable to generate requestable event CPULoad
      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      Unable to generate requestable event CPULoad

      REPRODUCIBILITY :
      This bug can be reproduced always.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: