[ https://jira.jboss.org/browse/EMBJOPR-316?page=com.atlassian.jira.plugin.... ] Ian Springer resolved EMBJOPR-316. ---------------------------------- Resolution: Rejected This is expected behavior, since most (or possibly all) of the properties from datasource configurations require an app server restart for changes to their values to take effect. Under the covers the RHQ jboss-as-5 plugin uses the Profile Service to update configuration properties of datasources, topics, etc. Specifically, it updates the managed properties on a managed component object and then calls ManagementView.updateComponent(managedComponent) to tell the Profile Service to update the properties. However, only some properties will be immediately updated in the runtime; others will require an restart of the app server for the new values to take effect. This is referred to as the property's "activation policy". Each property exposes its activation policy via managedProperty.getActivationPolicy(). An activation policy of IMMEDIATE means the new value will go into effect immediately, whereas a policy of RESTART indicates the app server must be restarted. Unfortunately, the RHQ platform's configuration subsystem does not currently provide a mechanism to expose the concept of activation policy, which means there's no standardized way for the admin-console Configuration tab to indicate for each property whether or not a restart is required. The best we can do until activation policy support is added to RHQ is to add a "App server restart required for changes to take effect." note to the description of each property which has a policy of RESTART. I will create an issue in RHQ Bugzilla to track adding support for activation policy and for improving property descriptions in the mean time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira