My agent shutdown was hanging (note, I expect eventually the agent kill logic would have kicked in) so I checked the log: In one minute intervals: 2009-04-22 10:39:36,189 DEBUG [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Asked to remove an unknown Resource [Resource[id=500628, type=JBoss ESB Listeners, key=jboss.esb:deployment=jbossesb.esb,listener-name=redeliver-scheduled-listener,service-category=JBossESB-Internal,service-name=RedeliverService, name=redeliver-scheduled-listener - JBossESB-Internal Listener Configuration, parent=RedeliverService Service]] with UUID [982c1313-814d-4e8c-be98-a73ee53b9327] 2009-04-22 10:39:36,189 DEBUG [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Removing Resource[id=500629, type=Actions, key=RedeliverMessagesAction , name=RedeliverMessagesAction , parent=RedeliverService Service] from local inventory... 2009-04-22 10:40:36,186 WARN [InventoryManager.discovery-1] (org.rhq.core.pc.PluginContainer)- There may be a deadlock in the plugin container. java.lang.Throwable: There may be a deadlock in the plugin container. at org.rhq.core.pc.PluginContainer.obtainReadLock(PluginContainer.java:346) at org.rhq.core.pc.PluginContainer.getMeasurementManager(PluginContainer.java:420) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:866) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:858) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:858) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:858) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:858) at org.rhq.core.pc.inventory.InventoryManager.removeResourceAndIndicateIfScanIsNeeded(InventoryManager.java:858) at org.rhq.core.pc.inventory.InventoryManager.removeResource(InventoryManager.java:828) at org.rhq.core.pc.inventory.InventoryManager.purgeObsoleteResources(InventoryManager.java:2035) at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:732) at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:701) at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:118) at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:70) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) 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:619) 2009-04-22 10:40:36,186 DEBUG [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Asked to remove an unknown Resource [Resource[id=500629, type=Actions, key=RedeliverMessagesAction , name=RedeliverMessagesAction , parent=RedeliverService Service]] with UUID [173f3a41-a49c-4247-bb9d-ab21e81c1b2c] 2009-04-22 10:41:36,184 WARN [InventoryManager.discovery-1] (org.rhq.core.pc.PluginContainer)- There may be a deadlock in the plugin container. java.lang.Throwable: There may be a deadlock in the plugin container.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2004
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Mazz, any insight on this one?
I have never seen this, but I know of nothing that explicitly attempted to fix this. It's possible this problem still exists, we've just never seen it again. I would leave this around, or close it as cannot-reproduce or something like that.
cannot reproduce this. closing unless and until someone reproduces this and can provide more information. I suspect in the intervening 2 years since this was reported (and never seen again since) that we've inadvertently fixed this with the refactorings that have since gone into the PC.