Red Hat Bugzilla – Bug 820667
Document reload needed behavior
Last modified: 2012-07-09 16:34:04 EDT
Created attachment 583623 [details]
See Bug 820623
Some changes that are made to as7 servers do not become effective immediately, but only after a reload.
As RHQ/JON has no general way of conveying out-of-band information like this from the agent to the UI/ user, the configuration editor will ask the server when a live configuration is fetched if a reload is needed and will show a yellow bar (see screenshot).
This is far from perfect, as e.g. operations that put the as7 server into "need reload" state are not captured that way. Same for addition of child resources.
As a workaround, the user can go to the config tab (of any of the resources of the server) and if that shows the yellow bar, go to the base server resource and trigger a reload
Note that if the server was in the need reload state and the agent goes down and the user hits the configuration page, this yellow note will be displayed even if the target server has been reloaded meanwhile.
In the EAP 6 docs here:
Click Inventory -> Click Servers -> Click EAP6 -> click transactions -> configuration -> Recovery Listener check No from Yes -> Click Save-> Click on EAP server again -- yellow message is being shown asking to reload server -> click EAP -> Operations -> New Schedule -> choose reload from drop down list -> click schedule Now.
no changes are being set before the reload.