Hide Forgot
Description of problem: mod-cluster configuration properties do not persist EAP restart Version-Release number of selected component (if applicable): EAP4.2 How reproducible: Steps to Reproduce: 1. change a mod-cluster configuration property 2. observe change is persisted to EAP's JMX console 3. restart EAP 4. observe change is no longer persisted to EAP's JMX console Actual results: Expected results: Configuration properties are persisted and survive EAP restart Additional info: link to JMX console: http://localhost/jmx-console/HtmlAdaptor?action=inspectMBean&name=Catalina%3Atype%3DModClusterListener
The bug has been fixed. Updating just the JMX properties does not send the properties to the http server as expected. Also, those settings are not persisted so any changes are lost after a server restart. Implemented a three step process to update, propagate, and persist configuration updates. The correct procedure to update mod_cluster properties for JBoss 42 is: 1) update JMX properties - nothing gets persisted in this step 2) invoke refresh command to propagate updates to httpd 3) persist changes server configuration file so that they are reloaded after a restart
http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=438c31bc4
verified RHQ 4.1.1 BETA. changed property flushpackets, bounced EAP, verified configuration still set.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE