Avoid printing unwanted warning to stdout for hsperf file issues

XMLWordPrintable

      Prior to JDK-8286030, the JVM could crash if several instances tried to access the same hsperf file at the same time. JDK-8286030 fixed the crash, but added a warning message if a race is detected. Unfortunately, this message is printed to stdout, a problem which is only exaggerated by the fact that it is rare and quite unexpected, so it causes intermittent failures.

      This causes problem with the build (see JDK-8327099), but some googling indicates that this is also causing real-world problems for other users as well (see e.g. https://stackoverflow.com/q/79559390, https://github.com/apache/arrow/issues/39113)

      At the very least, any error message should be printed to stderr. In general, I think the JVM should be extremely reluctant to print anything at all to stdout or stderr, since it will interfere with the user application running.

            Assignee:
            David Holmes
            Reporter:
            Magnus Ihse Bursie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: