| Summary: | Configuring the RHQ Storage node running as Windows service cannot be done using rhq-storage-wrapper files | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> |
| Component: | Storage Node | Assignee: | Michael Burman <miburman> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | JON 3.3.4 | CC: | fbrychta, jmartine, loleary |
| Target Milestone: | ER01 | Keywords: | Triaged |
| Target Release: | JON 3.3.6 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-07 14:27:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
bkramer
2016-01-25 12:57:05 UTC
It seems that additional properties in rhq-storage-wrapper.inc are totally ignored. Another way how to set heap is in rhq-storage-wrapper.env. However it's actually changed (visible in process cmdline parameters) it's not changed in UI. "rhq-storage-wrapper.conf" recommends to avoid customize that file, instead use "rhq-storage-wrapper.inc" and "rhq-storage-wrapper.env". However, "rhq-storage-wrapper.env" says: #***************************************************************************** # MANAGED SETTINGS # # This section represents the values managed as RHQ Storage Node resource # configuration values. Or, set by the installer. # # DO NOT EDIT THESE VALUES BY HAND. Changes should be performed via # the Administration section of the RHQ GUI. # #***************************************************************************** ... set.heap_min=-Xms512M set.heap_max=-Xms512M ... So we shouldn't mess with those values, is not intended to work in that way. At this point, Bug 1299448 has been fixed, I vote to use that one instead. |