Description of problem:
Resources using ResourceContext.createAvailablityCollectorRunnable() to enable async availability collections are unable to do so when they are being restored
from the persistent storage during plugin container start up.
The AvailabilityCollectorThreadPool is only initialized *after* the resources are loaded from disk and activated, and therefore the above call will always end up with an exception (because the thread pool is null by the time the resources are started up).
Version-Release number of selected component (if applicable):
RHQ 3.0.0 and up
Steps to Reproduce:
1. Inventory JBoss AS 5 resource, set the "Availability Check Period" property to a valid value.
2. restart the agent
The JBoss AS 5 resource is forever down
the resource is up and async availability collection is working
in case of JBoss AS 5 resource, the workaround is unset the above mentioned property in its connection settings. This will prevent the resource from trying the async avail collection and fall back to detecting it synchronously.
Author: Lukas Krejci <firstname.lastname@example.org>
Date: Wed Oct 12 12:25:22 2011 +0200
BZ 711502 - make sure the availability collectors are initialized before any resource component is started.
observed BZ 744803 while verifying this.
this is verified by following the reproduction steps
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE