Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

NPE: Unexpected error running autodiscoverer for plugin: WebSphere Admin 6.1 or 7.0: null

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.3.0-EE-1408 running on CentOS 5.4
    HQ-agent 4.3.0-EE-1408 running on CentOS 5.3 with WebSphere 6.1 installed
  • Case Links:
    none
  • Regression:
    No

Description

After upgrading agent and stoping/restarting the agent, the following is shown in the agent.log:

2010-04-14 13:07:47,294 INFO [Thread-6] [RuntimeAutodiscoverer] Running runtime autodiscovery for WebSphere Admin 6.1
2010-04-14 13:07:47,776 ERROR [Thread-6] [RuntimeAutodiscoverer] Unexpected error running autodiscoverer for plugin: WebSphere Admin 6.1: null
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:595)
at org.hyperic.util.config.ConfigResponse.setValue(ConfigResponse.java:149)
at org.hyperic.hq.plugin.websphere.jmx.WebsphereRuntimeDiscoverer.discoverServers(WebsphereRuntimeDiscoverer.java:311)
at org.hyperic.hq.plugin.websphere.WebsphereAdminDetector.discoverServers(WebsphereAdminDetector.java:65)
at org.hyperic.hq.product.ServerDetector.discoverResources(ServerDetector.java:209)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)

Expected Result:
No errors reported in log when starting hq-agent

Actual Result:
Unexpected error running autodiscoverer for plugin: WebSphere Admin 6.1 or 7.0 : null reported

Steps to reproduce:
1. Install hq-agent on machine running WebSphere 6.1 or 7.0
2. Start hq-agent
3. Look at agent .log file
4. Note reported error

Work around:
N/A - does not appear to affect functionality???

Activity

Hide
Todd Rader added a comment -

The null value was for admin port, so somehow the upgrade caused that value to be lost.

Show
Todd Rader added a comment - The null value was for admin port, so somehow the upgrade caused that value to be lost.
Hide
Frederic Calindas added a comment -

This isue was reproducible using build 1411 with WebSphere Admin 7.0 on CentOS 5.3 as well:

2010-04-19 14:56:34,152 INFO [ScheduleThread] [CollectorThread] CollectorThread started
2010-04-19 14:56:35,617 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: The "name" parameter cannot be null.
2010-04-19 14:56:35,661 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: resolve(WebSphere:name=JVM,type=JVM,j2eeType=JVM,J2EEServer=%server.name%,node=vmlin-was-01Node01,): WebSphere:name=JVM,type=JVM,j2eeType=JVM,J2EEServer=%server.name%,node=vmlin-was-01Node01, query returned 0 results
2010-04-19 14:56:35,689 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: The "name" parameter cannot be null.
2010-04-19 14:56:36,978 INFO [Thread-6] [RuntimeAutodiscoverer] Running runtime autodiscovery for WebSphere 7.0
2010-04-19 14:56:38,423 INFO [Thread-6] [RuntimeAutodiscoverer] WebSphere 7.0 discovery took 1.32
2010-04-19 14:56:38,423 INFO [Thread-6] [RuntimeAutodiscoverer] Running runtime autodiscovery for WebSphere Admin 7.0
2010-04-19 14:56:38,679 ERROR [Thread-6] [RuntimeAutodiscoverer] Unexpected error running autodiscoverer for plugin: WebSphere Admin 7.0: null
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:770)
at org.hyperic.util.config.ConfigResponse.setValue(ConfigResponse.java:149)
at org.hyperic.hq.plugin.websphere.jmx.WebsphereRuntimeDiscoverer.discoverServers(WebsphereRuntimeDiscoverer.java:314)
at org.hyperic.hq.plugin.websphere.WebsphereAdminDetector.discoverServers(WebsphereAdminDetector.java:69)
at org.hyperic.hq.product.ServerDetector.discoverResources(ServerDetector.java:209)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)

Show
Frederic Calindas added a comment - This isue was reproducible using build 1411 with WebSphere Admin 7.0 on CentOS 5.3 as well: 2010-04-19 14:56:34,152 INFO [ScheduleThread] [CollectorThread] CollectorThread started 2010-04-19 14:56:35,617 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: The "name" parameter cannot be null. 2010-04-19 14:56:35,661 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: resolve(WebSphere:name=JVM,type=JVM,j2eeType=JVM,J2EEServer=%server.name%,node=vmlin-was-01Node01,): WebSphere:name=JVM,type=JVM,j2eeType=JVM,J2EEServer=%server.name%,node=vmlin-was-01Node01, query returned 0 results 2010-04-19 14:56:35,689 ERROR [ScheduleThread] [ScheduleThread] Measurement plugin error: The "name" parameter cannot be null. 2010-04-19 14:56:36,978 INFO [Thread-6] [RuntimeAutodiscoverer] Running runtime autodiscovery for WebSphere 7.0 2010-04-19 14:56:38,423 INFO [Thread-6] [RuntimeAutodiscoverer] WebSphere 7.0 discovery took 1.32 2010-04-19 14:56:38,423 INFO [Thread-6] [RuntimeAutodiscoverer] Running runtime autodiscovery for WebSphere Admin 7.0 2010-04-19 14:56:38,679 ERROR [Thread-6] [RuntimeAutodiscoverer] Unexpected error running autodiscoverer for plugin: WebSphere Admin 7.0: null java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:770) at org.hyperic.util.config.ConfigResponse.setValue(ConfigResponse.java:149) at org.hyperic.hq.plugin.websphere.jmx.WebsphereRuntimeDiscoverer.discoverServers(WebsphereRuntimeDiscoverer.java:314) at org.hyperic.hq.plugin.websphere.WebsphereAdminDetector.discoverServers(WebsphereAdminDetector.java:69) at org.hyperic.hq.product.ServerDetector.discoverResources(ServerDetector.java:209) at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272) at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205) at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165) at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41) at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
Hide
German Laullon added a comment -

Frederic,

Can you add this line to the agente.properties and restart the agent?

log4j.logger.org.hyperic.hq.plugin.websphere.jmx.WebsphereRuntimeDiscoverer=debug

Show
German Laullon added a comment - Frederic, Can you add this line to the agente.properties and restart the agent? log4j.logger.org.hyperic.hq.plugin.websphere.jmx.WebsphereRuntimeDiscoverer=debug
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic roadmap make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic roadmap and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic roadmap make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic roadmap and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    37 weeks, 2 days ago