Bug 1017059 - After :server-set-restart-required operation web console shows reload required message
Summary: After :server-set-restart-required operation web console shows reload require...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER1
: EAP 6.4.0
Assignee: Heiko Braun
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1176535
TreeView+ depends on / blocked
 
Reported: 2013-10-09 08:25 UTC by Ondrej Chaloupka
Modified: 2019-08-19 12:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Enhancement


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-438 0 Major Resolved Reload/Restart required messages 2017-08-15 12:25:00 UTC

Description Ondrej Chaloupka 2013-10-09 08:25:28 UTC
When you run operation :server-set-restart-required() under the response header is then
"response-headers" => {"process-state" => "restart-required"}

(in in contrast to the response header after reload needed operation looks like:
"response-headers" => {"process-state" => "reload-required"})

But the web console shows message 
"A server reload is required!"

This should be differentiate to user know whether reload or restart is needed. The console should show clear info that server is needed to be restarted.



In fact the whole info message is a bit strange (when you click on its detail in the right top corner). It's said:
Wed Oct 09 10:12:20 GMT+200 2013
A server reload is required!
Restart Required
 - Standlone Server
is it mean that reload or restart is required? It should be nice to have the message a bit clearer.

Comment 1 JBoss JIRA Server 2014-07-03 07:24:07 UTC
Heiko Braun <ike.braun@googlemail.com> updated the status of jira HAL-438 to Resolved

Comment 2 Pavel Jelinek 2014-11-26 09:30:57 UTC
Should this still remain in POST state?

Comment 3 Jakub Cechacek 2014-12-05 10:27:15 UTC
Setting up missing flags and target release

Comment 4 Jakub Cechacek 2014-12-09 12:04:55 UTC
Simply changing the message to "The server configuration needs to be reloaded or the server restarted!" does not change anything as it is still not clear what action is required. 

It is also confusing because of the "Reload" button which is displayed. It leads user to think that reloading the server will help and then when the action is performed and nothing changes it may look like something is wrong.

Comment 5 Pavel Jelinek 2015-01-15 11:27:34 UTC
Verified for EAP 6.4.0.ER1


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