Fedora Account System
Red Hat Associate
Red Hat Customer
2012-05-04 10:44:48,159 ERROR [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Failed to start component for Resource[id=13454, uuid=1402beb9-1025-4a36-a9d4-4862d948a200, type={jboss-as-7}Deployment, key=server-group=main-server-group,deployment=test-simple.war, name=test-simple.war, parent=main-server-group] from synchronized merge. org.rhq.core.clientapi.agent.PluginContainerException: Failed to start component for resource Resource[id=13454, uuid=1402beb9-1025-4a36-a9d4-4862d948a200, type={jboss-as-7}Deployment, key=server-group=main-server-group,deployment=test-simple.war, name=test-simple.war, parent=main-server-group]. at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1701) at org.rhq.core.pc.inventory.InventoryManager.refreshResourceComponentState(InventoryManager.java:2910) at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2661) at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2667) at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2667) at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2667) at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:1085) at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:1059) at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.call(AutoDiscoveryExecutor.java:126) at org.rhq.core.pc.inventory.AutoDiscoveryExecutor.run(AutoDiscoveryExecutor.java:88) 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:680) Caused by: java.lang.NullPointerException at org.rhq.modules.plugins.jbossas7.DeploymentComponent.determineDeploymentFile(DeploymentComponent.java:240) at org.rhq.modules.plugins.jbossas7.DeploymentComponent.start(DeploymentComponent.java:60)
Urgent as the NPE prevents the component start
Hmm... I can fix that NPE, but I was wondering how your deployment looks like in the JBoss console?
master http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=2eae9024a1fe4d54b14e9de44cf41a1bed831c6c Author: Lukas Krejci <lkrejci> Date: Fri May 4 11:15:56 2012 +0200 [BZ 818870] - Defensive null check when determining the content location of a deployment during DeploymentComponent start.
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.