Bug 534251 (RHQ-1065) - NPE in EmbeddedJMXServerDiscoveryComponent
Summary: NPE in EmbeddedJMXServerDiscoveryComponent
Keywords:
Status: CLOSED NEXTRELEASE
Alias: RHQ-1065
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 1.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Jeff Weiss
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-06 05:58 UTC by John Mazzitelli
Modified: 2014-11-09 22:48 UTC (History)
1 user (show)

Fixed In Version: 1.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description John Mazzitelli 2008-11-06 05:58:00 UTC 
2008-11-05 23:54:06,641 WARN  [InventoryManager.discovery-1] (rhq.core.pc.inventory.RuntimeDiscoveryExecutor)- Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Server, name=JBoss AS JVM, plugin=JBossAS]
java.lang.NullPointerException
        at org.rhq.plugins.jmx.EmbeddedJMXServerDiscoveryComponent.discoverResources(EmbeddedJMXServerDiscoveryComponent.java:60)
        at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246)
        at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218)
        at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136)
        at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97)
        at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54)
        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)
Comment 1 Heiko W. Rupp 2008-11-06 10:15:31 UTC 
Are you running with native turned off?
Comment 2 John Mazzitelli 2008-12-13 06:06:32 UTC 
yes, I probably did not have native enabled. fixed this NPE by checking to see if the native process was null or not. if null, skip the processing.
Comment 3 Jeff Weiss 2009-01-09 19:29:09 UTC 
Ran discovery with native turned off, didn't see any errors.  rev2561
Comment 4 Red Hat Bugzilla 2009-11-10 20:23:09 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1065
Note You need to log in before you can comment on or make changes to this bug.