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

on windows 64, can't easily manage 64 bit jre for hq agent and 32 bit jre for hq server

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.0.0, 4.1.0, 4.2.0
  • Fix Version/s: None
  • Component/s: None
  • Environment:
    Windows 64 bit
  • Case Links:
    none
  • Regression:
    No

Description

I've had some challenges running both an HQ server plus an HQ agent on the same Windows 64-bit box. The gist of it is that if you set HQ_JAVA_HOME as a system env var (required for services), then it affects both the HQ server and agent. If we've got a jmx-secured tc server running (i.e. password encrypted by 64 bit JVM), then we really want the HQ agent running a 64 bit jre - and the server MUST run 32 bit jre.

I cheated around this by setting HQ_JAVA_HOME to 32 bit when starting the server, then changing HQ_JAVA_HOME to 64 bit for starting the agent. This is extremely awkward when restarting services.

This issue pertains to development environments; I understand that in production environments, the server should be running standalone.

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

Dates

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