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

postgresql-plugin doesn't release db connections when reconfigured

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5, 4.6.0.1
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    PG 8.3 on linux
  • Case Links:
  • Regression:
    No

Description

Steps to reproduce:

  • Configure any PostgreSQL 8.x server with valid creds and set the jdbcUrl to connect to a database (like template1) that the user configured can connect to.
  • Once the agent connects and starts logging metrics, change the jdbcUrl to connect to a different database (or just /). It doesn't even matter if the agent has permissions for the database and in my case I had errors in the agent log as I intentionally set the url to something the agent shouldn't be able to connect to.
  • Look at the open connections in postgres. A 'select datname from pg_stat_activity;' shows that the hq agent still has a connection open to the initial database.

Actual Results:
The connection that is still open should be closed when the resource is configured for a different database. Restarting the agent is required to close the connection currently.

Expected Results:
The connection should be closed

Activity

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 (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 4 days ago