Bug 820667

Summary: Document reload needed behavior
Product: [Other] RHQ Project Reporter: Heiko W. Rupp <hrupp>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: ahovsepy, hrupp
Target Milestone: ---   
Target Release: JON 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-09 20:34:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 707223    
Attachments:
Description Flags
Screenshot none

Description Heiko W. Rupp 2012-05-10 15:57:25 UTC 
Created attachment 583623 [details]
Screenshot

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.
Comment 1 Deon Ballard 2012-06-28 20:01:06 UTC 
In the EAP 6 docs here:
http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/How_to_Manage_JBoss_Servers/reload-config.html
Comment 2 Armine Hovsepyan 2012-07-03 15:19:55 UTC 
verified.

verification case:

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.