Red Hat Bugzilla – Bug 1313969
Reload operation is showing "restart" in Operations history.
Last modified: 2017-01-02 08:24:05 EST
Created attachment 1132412 [details] EAP-operations-performed Description of problem: Reload operation is showing "restart" in Operations history. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Login to JON server 2. Navigate to the imported EAP standalone Server 3. Navigate to Operations tab 4. initiate "reload" operation Actual results: Restarting whole Standalone server an showing "restart" in Operations history. Expected results: It should reload the configuration and show "reload" in operation history Additional info:
I am not sure I get this. The display names of the operations show here are literally taken from the value in the plugin descriptor (with capitalization done). So when I see the screenshot, I understand you indeed were running "restart". Apart from that: EAP does indeed for "reload" internally mostly shut down, and then restart - this looks in the log file like the server is entirely restarting. The difference to restart though is that the JVM is not terminated on reload, while it is terminated and a new one started for "restart".
I can't repeat this, I get "Reload" when I do "Reload". And like Heiko described, if the operation name states "Reload" then that's repeated, there's no second description part or reading of the operation name from elsewhere. And there's no difference to EAP6 or any other plugin/resource. I'd say CLOSED -> NOTABUG.