RFR: 8275375: jfr/api/consumer/security/TestStreamingRemote.java fails with AccessControlException
Erik Gahlin
egahlin at openjdk.java.net
Mon Oct 18 02:49:54 UTC 2021
On Mon, 18 Oct 2021 01:52:22 GMT, Yasumasa Suenaga <ysuenaga at openjdk.org> wrote:
> We can see AccessControlException in some JFR tests since [JDK-8271949](https://bugs.openjdk.java.net/browse/JDK-8271949). It is caused that SecurityException happens in both `File::canWrite` and `Path::toRealPath`. We should fall-through with empty path because the path will be evaluated when emergency dump happens.
Why do you get a SecurityException?
This doesn't happen with "JFR.start filename=...." and is ignoring the path (and logging) really the correct way to handle it?
I would expect jcmd users to be informed (in their client) if there is a problem, similar to other incorrect options with JFR.configure. Logging in JVM process seems incorrect (and also the log tag set, JFR_DCMD seems more appropriate).
-------------
PR: https://git.openjdk.java.net/jdk/pull/5984
More information about the hotspot-jfr-dev
mailing list