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

NullPointerException in AlertDefinitionManagerImpl.findAllAlertDefinitions(AuthzSubject)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.5.1
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    I think all version since 4.2.
  • Case Links:
    none
  • Regression:
    No

Description

Just logging this in case the behaviour is not expected.

select * from EAM_ALERT_DEFINITION always returns first row(ID = 0) with "Resource Type Alert". AlertDefinitionManagerImpl.findAllAlertDefinitions(AuthzSubject) is throwing NullPointer from:
java.lang.NullPointerException
at org.hyperic.hq.events.server.session.AlertDefinition.getAppdefType(AlertDefinition.java:220)
at org.hyperic.hq.events.server.session.AlertDefinition.getAppdefEntityId(AlertDefinition.java:530)
at org.hyperic.hq.events.server.session.AlertDefinitionManagerImpl.findAllAlertDefinitions(AlertDefinitionManagerImpl.java:1165)

because alert def RESOURCE_ID is always null for definition created during the install.

AlertDefinitionManagerImpl.findAllAlertDefinitions(AuthzSubject) is called from org.hyperic.hq.bizapp.server.session.EventsBossImpl.findAllAlertDefinitions(int) but I can't see if someone is using that function.

Activity

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 road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map 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 road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map 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 (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks ago