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

No display name when JVM is launched from custom native code.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: P2 P2
    • None
    • 7u40
    • core-svc

      When finding and visualizing locally discovered JVMs, Mission Control uses the following way to find out the name to use when visualizing the connection:

      VirtualMachineDescriptor#getDisplayName()

      For some applications with custom launchers, such as NetBeans and VisualVM, this returns the empty string. It would be nice if at least the FQN of the main class could be returned instead.

            Unassigned Unassigned
            hirt Marcus Hirt
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: