RFR: 8234466: Class loading deadlock involving X509Factory#commitEvent()

[Chris Hegarty]

> On 13 Jan 2020, at 13:14, Daniel Fuchs <daniel.fuchs at oracle.com> wrote:
> 
> On 13/01/2020 10:28, Seán Coffey wrote:
>> some off line comments suggested that I could move the jar initialization checks to the EventHelper class. With that in place, the EventHelper utility class should never initialize the logging framework early during jar initialization.
>> http://cr.openjdk.java.net/~coffeys/webrev.8234466.v4/webrev/
> 
> Looks good to me Seán. Probably safer than the other alternatives.

+1

I’m going to ask, since I cannot find the answer myself. Why are some securityLogger::log invocations guarded with isLoggingSecurity, and others not? With this change shouldn’t all invocations be guarded, since it is isLoggingSecurity that assigns securityLogger a value?

-Chris