|date:||2009-11-10 01:01:12 UTC (6 years)|
The "isHidden" feature was obviously committed too early (by me).
It would throw a RuntimeException which went all the way back to
MonitoringBootstrap -- whenever a "hidden" probe was discovered.
I.e. it was a routine and normal occurrence yet it was treated like an error.
2 things --
1. if it is hidden do NOT add it as a DTrace listener to the probe -- handle it
QUIETLY and uneventfully.
2. If *all* the methods in a PP are hidden -- then don't even create the DTrace
I tested manually and everything looks good.
JDK6 - V3 - DTrace turned off on Solaris10 --> no problems, QL passed
JDK6 - V3 - DTrace turned on on Solaris10 --> no problems
glassfish-dtrace copied to modules dir and JDK7 runtime setup
JDK7 - V3 - glassfish-dtrace copied to modules DTrace turned off on Solaris10 --> no problems
JDK7 - V3 - DTrace turned on on Solaris10 --> no problems - works!