Bug 1259554
Summary: | Changing the Storage Node JMX port does not update the JMX connection URL | |||
---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Sanda <jsanda> | |
Component: | Core Server, Storage Node | Assignee: | Thomas Heute <theute> | |
Status: | ON_QA --- | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.13 | CC: | hrupp, theute | |
Target Milestone: | --- | |||
Target Release: | RHQ 4.14 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1259555 (view as bug list) | Environment: | ||
Last Closed: | Type: | Bug | ||
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1259555 |
Description
John Sanda
2015-09-03 02:58:02 UTC
I left out a key detail in the description. The jmx_port property in cassandra-jvm.properties does get updated and the storage node gets restarted so that the port change takes effect. The agent can no longer connect to the storage node via JMX, and it is reported down. jmx_port from cassandra-jvm.properties always shows up on command line. So I think it is not relevant. I am going to fix resource upgrade code within StorageNodeDiscoveryComponent branch: master link: https://github.com/rhq-project/rhq/commit/021df29a5 time: 2015-09-03 14:14:27 +0200 commit: 021df29a527b6c3e334abe305005038915883314 author: Libor Zoubek - lzoubek message: Bug 1259554 - Changing the Storage Node JMX port does not update the JMX connection URL Fix upgrade facet impl. of StorageNodeDiscoveryComponent. We're now able to detect JMX port change at agent/pc startup time |