RVM
  1. RVM
  2. RVM-127

Implement the VM interfaces for the management beans

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1000
    • Component/s: Runtime: JMX
    • Labels:
      None
    • Number of attachments :
      0

      Description

      The first focus of the JMX support for Jikes RVM is on providing an implementation of the existing VM interfaces, so that none of them fail due to the lack of a VM implementation.

      The trickest parts will be handling memory management and threading, as these are fairly complex interfaces. It is possible that not all optional facilities will be provided at this stage.

        Activity

        Hide
        Erik Brangs added a comment -

        Removing assignees of all issues where the assignee has not contributed to Jikes RVM for quite some time or where the assignee is no longer a member of the core team.

        If you are affected and would like to work on one of the issues, please drop me a note (or change the assignee yourself if you have the necessary permissions).

        Show
        Erik Brangs added a comment - Removing assignees of all issues where the assignee has not contributed to Jikes RVM for quite some time or where the assignee is no longer a member of the core team. If you are affected and would like to work on one of the issues, please drop me a note (or change the assignee yourself if you have the necessary permissions).
        Hide
        Erik Brangs added a comment -

        After we're done with the subtasks, the following beans will still be missing:

        • OperatingSystemMXBean (implemented by GNU Classpath, we only need to provide the method getSystemLoadAverage )
        • PlatformLoggingMXBean (Java 7, not in GNU Classpath git HEAD right now)
        • BufferPoolMXBean (Java 7, not in GNU Classpath git HEAD right now)
        Show
        Erik Brangs added a comment - After we're done with the subtasks, the following beans will still be missing: OperatingSystemMXBean (implemented by GNU Classpath, we only need to provide the method getSystemLoadAverage ) PlatformLoggingMXBean (Java 7, not in GNU Classpath git HEAD right now) BufferPoolMXBean (Java 7, not in GNU Classpath git HEAD right now)
        Hide
        Andrew John Hughes added a comment -

        Is JikesRVM still using GNU Classpath? I've been doing a bit of work there recently, and adding the missing beans is certainly feasible if there's interest.

        getSystemLoadAverage does have a default native implementation in vm/reference.using getloadavg; see native/jni/java-lang/gnu_java_lang_management_VMOperatingSystemMXBeanImpl.c

        Show
        Andrew John Hughes added a comment - Is JikesRVM still using GNU Classpath? I've been doing a bit of work there recently, and adding the missing beans is certainly feasible if there's interest. getSystemLoadAverage does have a default native implementation in vm/reference.using getloadavg; see native/jni/java-lang/gnu_java_lang_management_VMOperatingSystemMXBeanImpl.c
        Hide
        Erik Brangs added a comment -

        Yes, we're still using GNU Classpath. Open JDK support is not yet ready.

        I'm not sure if there's enough interest in JMX by somebody in the Jikes RVM community to warrant further work. It's been a long time since anybody asked for it.

        Personally, I don't need any of the JMX beans that I mentioned above. I've worked on JMX because I want to have an implementation of the threading bean features so that I can use JUnit timeouts without getting an UnsatisfiedLinkError (see RVM-692). I've merged the rest of the JMX features because the code was already written and it just doesn't make sense to let it bitrot any longer.

        Show
        Erik Brangs added a comment - Yes, we're still using GNU Classpath. Open JDK support is not yet ready. I'm not sure if there's enough interest in JMX by somebody in the Jikes RVM community to warrant further work. It's been a long time since anybody asked for it. Personally, I don't need any of the JMX beans that I mentioned above. I've worked on JMX because I want to have an implementation of the threading bean features so that I can use JUnit timeouts without getting an UnsatisfiedLinkError (see RVM-692 ). I've merged the rest of the JMX features because the code was already written and it just doesn't make sense to let it bitrot any longer.

          People

          • Assignee:
            Andrew John Hughes
            Reporter:
            Andrew John Hughes
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 7 weeks
              7w
              Remaining:
              Time Spent - 2 weeks, 9 hours Remaining Estimate - 4 weeks
              4w
              Logged:
              Time Spent - 2 weeks, 9 hours Remaining Estimate - 4 weeks Time Not Required
              2w 9h