Description of problem: The JMX plugin ignores readOnly properties of a configuration and tries to set them through JMX setters. If the setter is not available, this will fail the whole configuration update (according to the UI, but in reality some of the values will be set). Version-Release number of selected component (if applicable): 4.14 SNAPSHOT How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: readOnly values are threated as readOnly Additional info: