Bug 728989 - mod-cluster configuration properties do not persist EAP restart
Summary: mod-cluster configuration properties do not persist EAP restart
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.1
Hardware: All
OS: All
medium vote
Target Milestone: ---
: ---
Assignee: Stefan Negrea
QA Contact: Mike Foley
Depends On:
Blocks: 682349
TreeView+ depends on / blocked
Reported: 2011-08-08 15:00 UTC by Mike Foley
Modified: 2012-02-07 19:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-02-07 19:18:59 UTC

Attachments (Terms of Use)

Description Mike Foley 2011-08-08 15:00:32 UTC
Description of problem:  mod-cluster configuration properties do not persist EAP restart

Version-Release number of selected component (if applicable):


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

Comment 1 Stefan Negrea 2011-08-28 16:12:52 UTC
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

Comment 3 Mike Foley 2011-08-30 15:12:08 UTC
verified RHQ 4.1.1 BETA.  changed property flushpackets, bounced EAP, verified configuration still set.

Comment 4 Mike Foley 2012-02-07 19:18:59 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE

Note You need to log in before you can comment on or make changes to this bug.