Monitoring bootstrap code is probing any directory under
lib/install/applications to resource adapters that may or may not contain
flashlight probes. This cause the connector class loader to be created and cause
a long list of modules to be resolved.
Solution : we should only probe RAs when they are deployed (used) rather than at
Possible extended solution : we should extend that mechanism to all deployments
so that any Java EE deployed application can ship probes and they would become
automatically registered with our monitoring/REST tree. I am already drooling at
For that, it might be as simple as writing a ProbeDeployer.