Whenever I deploy the package, the core bundle is deployed and activated first; then the factory configs in /apps/healthcheck/config/* get active and the respective HealthStatusProviders for the MBeans are created.
But: The bundle, which brings the services to create the MBeans, is not installed yet.
Therefor the results are void and useless, although they look good on the statuspage. The only indication is:
18.12.2012 18:53:49.206 INFO [0:0:0:0:0:0:0:1%0 [1355885629185] GET /content/statuspage.html HTTP/1.1] de.joerghoh.cq5.healthcheck.impl.providers.MBeanStatusProvider Ignoring property Resolv
edBundles.WARN.!=.0 (no such a JMX attribute ResolvedBundles)
How should we approach that? Can we delay the creation of the HealthStatusProvider services until the MBeans are there?
Whenever I deploy the package, the core bundle is deployed and activated first; then the factory configs in /apps/healthcheck/config/* get active and the respective HealthStatusProviders for the MBeans are created.
But: The bundle, which brings the services to create the MBeans, is not installed yet.
Therefor the results are void and useless, although they look good on the statuspage. The only indication is:
18.12.2012 18:53:49.206 INFO [0:0:0:0:0:0:0:1%0 [1355885629185] GET /content/statuspage.html HTTP/1.1] de.joerghoh.cq5.healthcheck.impl.providers.MBeanStatusProvider Ignoring property Resolv edBundles.WARN.!=.0 (no such a JMX attribute ResolvedBundles)
How should we approach that? Can we delay the creation of the HealthStatusProvider services until the MBeans are there?