AnsweredAssumed Answered

Why no InstrumentBootstrapClass matching all classes

Question asked by Fred.K on Jun 16, 2016
Latest reply on Jun 22, 2016 by Fred.K

A couple weeks ago I was curious if a poor entropy in /dev/random would affect SSL performance and so created a pbd to trace java.security.SecureRandom.

So I had this:

     IdentifyMatchingClassesAs: java.security.*  SecureRandom

     InstrumentBootstrapClass:  java.security.SecureRandom  true

The last line made me think of a couple of things:

  • why isn't there an InstrumentBootstrapMatchingClassesAs:  java.security.* true ?
  • while in this case I can understand the need for the InstrumentBootstrapClass, but are there any patterns to know which classes require this from the class list when you start your jvm with  -verbose:class

Outcomes