RFR (XS): 8172261: [JVMTI] Specification for early VM start event needs to lower expectations in relation class loading

David Holmes david.holmes at oracle.com
Wed Jan 18 05:04:09 UTC 2017


Thanks Serguei.

David

On 18/01/2017 2:53 PM, serguei.spitsyn at oracle.com wrote:
> David,
>
> It looks good.
> Thank you for taking care about this jck issue!
>
> Thanks,
> Serguei
>
>
>
> On 1/17/17 17:03, David Holmes wrote:
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8172261
>>
>> webrev: http://cr.openjdk.java.net/~dholmes/8172261/webrev/
>>
>> This is a simple relaxation of the spec in regards to the new "early
>> VM start" event, to explicitly allow for the possibility that
>> arbitrary class loading during this "early VM start" time may fail in
>> extreme ways.
>>
>> Changes are easier to see in text than webrev:
>>
>> Extend:
>>
>> The VM is capable of executing bytecode but it may not have
>> initialized to the point where it can load classes in modules other
>> than java.base.
>>
>> to read:
>>
>> The VM is capable of executing bytecode but it may not have
>> initialized to the point where it can load classes in modules other
>> than java.base, or even arbitrary classes in java.base.
>>
>> ---
>>
>> Replace:
>>
>> Care should also be taken with JNI FindClass as it may not be possible
>> to load classes that are not in the java.base module.
>>
>> with:
>>
>> Extreme care should also be taken with JNI FindClass as it may not be
>> possible to load classes, and attempts to do so may result in
>> unpredictable behavior, maybe even stability issues on some VM
>> implementations.
>>
>> ---
>>
>> Thanks,
>> David
>


More information about the serviceability-dev mailing list