Bug 1044594 - [WFLY-2663] mod_cluster metric properties are never applied
Summary: [WFLY-2663] mod_cluster metric properties are never applied
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: mod_cluster
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR0
: EAP 6.3.0
Assignee: Radoslav Husar
QA Contact: Michal Karm Babacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 15:58 UTC by Radoslav Husar
Modified: 2014-06-30 23:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of the mod_cluster subsystem configured load metrics and properties specified for them were parsed from the XML, but not applied to classes. This meant that configuring properties for load metrics did not have any effect. In this release, the properties are applied to the objects as expected.
Clone Of:
Environment:
Last Closed: 2014-06-28 15:27:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Radoslav Husar 2013-12-18 15:58:12 UTC 
Description of problem:
mod_cluster metric properties are parsed for but are never applied

Version-Release number of selected component (if applicable):
Whole 6.x tree


How reproducible:
Always


Steps to Reproduce:
1. setup a custom load metric with properties
2. start EAP

Actual results:
props are not applied


Expected results:
props are applied

Additional info:
n/a
Comment 1 Radoslav Husar 2013-12-18 15:59:02 UTC 
https://issues.jboss.org/browse/WFLY-2663
Comment 3 Michal Karm Babacek 2014-02-24 14:03:13 UTC 
Verified with 6.3.0.Alpha1 (DR0).
Comment 4 Radoslav Husar 2014-06-30 11:47:18 UTC 
Documentation: this is a bugfix, we should document this. People might not have been aware that these were never applied. It might break their existing custom load metrics in case they did not have correct configuration in previous versions.
Note You need to log in before you can comment on or make changes to this bug.