Proposal for back-porting JFR to OpenJDK8u

Andrew Haley aph at
Sat Dec 8 08:58:02 UTC 2018

On 12/7/18 9:54 PM, Hohensee, Paul wrote:

> My understand is that CSRs are not only for Java specification
> changes, but also for behavioral changes. E.g., I needed a CSR
> for a G1 JMX bugfix, see
> and the
> corresponding CSR

That seems excessive. Personally speaking, I am very much not in
favour of process for process's sake.

Oracle has its own way of doing things, and I suspect that some
of it is inntended to introduce some friction in order to
prevent excessive churn.

> Since bakporting JFR will produce different JVM behavior (well,
> new JVM behavior), I thought it might be necessary. If not, it
> makes things easier.

We might take a look at the JFR patches and decide that it's too
risky to commit them because of the amount of code that is
touched. It's hard to say without a clean set of patches.

So, we must prioritize stability, but let's go with easier if we

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the jdk8u-dev mailing list