JFR: Specification should say long and boolean, not Long or Boolean

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P3
    • 27
    • Affects Version/s: 25
    • Component/s: hotspot
    • None
    • jfr

      In various places in the jdk.jfr API specification, Long is being used when it really should be long. A null value is not valid, for example, for a threshold.

            Assignee:
            Erik Gahlin
            Reporter:
            Erik Gahlin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: