This should never happen ... Each of the DOWN resources has a Resource error like this: org.rhq.core.clientapi.agent.PluginContainerException: Failed to start component for resource Resource[id=10166, type=Plugin Container, key=rhq.pc:type=PluginContainer, name=Agent Plugin Container, parent=RHQ Agent]. at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1601) at org.rhq.core.pc.inventory.AvailabilityExecutor.checkInventory(AvailabilityExecutor.java:202) at org.rhq.core.pc.inventory.AvailabilityExecutor.checkInventory(AvailabilityExecutor.java:238) at org.rhq.core.pc.inventory.AvailabilityExecutor.checkInventory(AvailabilityExecutor.java:238) at org.rhq.core.pc.inventory.AvailabilityExecutor.call(AvailabilityExecutor.java:127) at org.rhq.core.pc.inventory.AvailabilityExecutor.run(AvailabilityExecutor.java:90) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IllegalStateException: No plugin class loader was specified for org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread@12ec7979. at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:548) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) ... 3 more I'm thinking this may be a plugin container bug. Note, I ran the "plugins update" Agent prompt command a couple times prior to noticing this issue.
Created attachment 535126 [details] screenshot
Created attachment 535143 [details] agent log containing various errors related to null plugin classloader and failing to init plugin classloader
[master b33a340] - ensure resource classloader is initialized in processSyncInfo() prior to making any resource component facet calls. QE, try running the "plugins update" Agent prompt command and then checking for Agent child resources being down or any other conspicuous availability-related problems.
Looks good in master.
Cherry-picked to release_jon3.x branch - commit ebdd048: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=ebdd048
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE