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

sun/tools/jstatd/TestJstatdDefaults.java failed with no such object in table

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P4
    • Resolution: Duplicate
    • Affects Version/s: 13
    • Fix Version/s: tbd
    • Component/s: core-svc
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      os_x

      Description

      execStatus=Failed. Execution failed\: `main' threw exception\: java.lang.RuntimeException\: Expected to get exit value of [0]

      More interesting info from the log:

      Start jstat:
      [/scratch/mesos/jib-master/install/jdk13-jdk.106/macosx-x64-debug.jdk/jdk-13/fastdebug/bin/jstat -J-XX:+UsePerfData -J-Duser.language=en -gcutil 91555@scaaa219.us.oracle.com 250 5]
      sun.jvmstat.monitor.MonitorException: Could not read data for remote JVM 91555
      at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.PerfDataBuffer.<init>(PerfDataBuffer.java:68)
      at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.RemoteMonitoredVm.<init>(RemoteMonitoredVm.java:71)
      at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:146)
      at jdk.jcmd/sun.tools.jstat.Jstat.logSamples(Jstat.java:107)
      at jdk.jcmd/sun.tools.jstat.Jstat.main(Jstat.java:70)
      Caused by: java.rmi.NoSuchObjectException: no such object in table
      at java.rmi/sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283)
      at java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260)
      at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
      at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209)
      at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161)
      at jdk.proxy1/com.sun.proxy.jdk.proxy1.$Proxy1.getCapacity(Unknown Source)
      at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.PerfDataBuffer.<init>(PerfDataBuffer.java:63)
      ... 4 more

      ProcessThread.stopProcess() will kill process

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mikael Mikael Vidstedt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: