Use a concurrent set implementation for the sampler tasks - consumer is
the self monitor and producer is the scheduling of new samplers.
log arrays as debug not as warning as that is known and currently (as
not requested yet) ok
added support for a new sampler attribute - reset-timeout in seconds. when set, the sampler will compare the number of selected metrics to the number of previously selected metrics after each connect. If both numbers are not equal, the input and selectors will be reset after this timeout so that metrics are re-selected. this should help in cases when metrics are partially selected during a server startup (e.g. slow weblogic startup) because not all JMX beans have already been registered. The actual timeout is a random value between 0.8*reset-timeout and 1.2*reset-timeout so that we do not synchronize multiple sampler resets and thus create CPU usage peaks.
throw configuration exception on missing shared resources and exit if any
exceptions are thrown during bootstrapping.
use daily rolling appender by default keeping 2 weeks of logs
Added the new reset-timeout option to the example