Skip to Main Content

Java HotSpot Virtual Machine

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Opening a jfr recording from a GraalVM native image is causing JMC to crash

Looking to add flight recordings to my graalvm applications, I've just built and run and successfully been recording, however; when I try to open this I have the application exit. The following is the full log of the application with the WARNING occurring when opening the file.

Java HotSpot(TM) 64-Bit Server VM warning: Option FlightRecorder was deprecated in version 13.0 and will likely be removed in a future release.
[0.331s][info][jfr,startup] Started recording 1.
[0.331s][info][jfr,startup] 
[0.331s][info][jfr,startup] Use jcmd 28393 JFR.dump name=JMC_Default filename=FILEPATH to copy recording data to file.
2022-12-21 20:37:38.214 jmc[28393:645956] +[CATransaction synchronize] called within transaction
2022-12-21 20:37:38.488 jmc[28393:645956] +[CATransaction synchronize] called within transaction
2022-12-21 20:37:40.436 jmc[28393:645956] +[CATransaction synchronize] called within transaction
2022-12-21 20:37:43.444 jmc[28393:645956] +[CATransaction synchronize] called within transaction
Dec 21, 2022 8:37:53 PM org.openjdk.jmc.flightrecorder.internal.parser.v1.ValueReaders$ReflectiveReader addField
WARNING: Could not find field with name 'virtual' in reader for 'thread'

I've included the macOS crash report as an attachment.
Java: 19.0.1; Java HotSpot(TM) 64-Bit Server VM 19.0.1+10-21
Runtime: Java(TM) SE Runtime Environment 19.0.1+10-21
System: Mac OS X version 13.1 running on x86_64; UTF-8; en_AU (nb)
macOS: Ventura 13.1
crash-report.txt (256.73 KB)

Comments

thatJeffSmith-Oracle Feb 13 2025

Your ENTRA users will get authenticated via JSON Web Tokens, and their Entra roles will determine which ORDS REST APIs they can hit.

When they hit an endpoint, it'll execute code in the database as the database user that owns the schema where the REST API is defined, not as Entra defiend end user. In fact, the Entra users won't have accounts in the database (they could, but wont' need to).

The :current_user field as far as ords is concerned would be the corresponding oauth2 client or JWT issued for the authorizied session.

Your prehook should be able to alter the session to set the context that would put your RLS/VPD security policy in play.

1 - 1

Post Details

Added on Dec 21 2022
1 comment
660 views