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

Errors in server log regarding couple of constants that already exist

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5, 4.x Sprint 10
  • Fix Version/s: None
  • Component/s: None
  • Environment:
    MySQL, CentOS, build #82, Large env (~1330 platforms)
  • Case Links:
    none

Description

Steps/scenario:

Stopped hq-server after some db deadlock errors
Start hq-server

During shut down and startup, the following errors appeared in the log, one instance of each both timees:

2010-08-31 15:08:05,601 ERROR [main] [org.apache.commons.validator.FormSet@238] Constant 'numeric' already exists in FormSet[default] - ignoring.
2010-08-31 15:08:05,602 ERROR [main] [org.apache.commons.validator.FormSet@238] Constant 'oid' already exists in FormSet[default] - ignoring.

Unsure of customer impact at this point, filing to track since it's an error but as minor since there is no obvious functionality impacted. Will re-prioritize after initial analysis.

Activity

Hide
Frederic Calindas added a comment -

This also occurs with 4.6.0 and embedded PostgreSQL DB with just new install server startup (no platforms).

Show
Frederic Calindas added a comment - This also occurs with 4.6.0 and embedded PostgreSQL DB with just new install server startup (no platforms).
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 (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks, 1 day ago