Bug 826008 - [eap6] notify user reload/restart is required is broken
Summary: [eap6] notify user reload/restart is required is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.5.0
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin 826031
TreeView+ depends on / blocked
 
Reported: 2012-05-29 10:40 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 826031 (view as bug list)
Environment:
Last Closed: 2013-09-01 10:03:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2012-05-29 10:40:35 UTC
Description of problem: When doing configuration changes to EAP6 user needs to be notified when EAP requires server reload.


Version-Release number of selected component (if applicable):
JON 3.1.ER6 EAP6.ER8

How reproducible:always 


Steps to Reproduce:
1.Force EAP to start sending "restart-required" response header (using CLI run :server-set-restart-required)
2. Check 'Configuration' tab of any server's child resource, yellow box signaling server reload should appear

1.Force EAP to start sending "reload-required" response header (Change configuration for mailSession resource)
2. Check 'Configuration' tab of any server's child resource, yellow box signaling server reload should appear 

Actual results:

Plugin does not signal either "reload-required" or "restart-required" response header

Expected results: our plugin should check "reload-required" and "restart-required" reponse-headers


Additional info:

Comment 1 Heiko W. Rupp 2012-05-29 12:17:34 UTC
restart is required - we were so far only reacting on reload-required

master 74bef966894fb0f

Comment 2 Heiko W. Rupp 2013-09-01 10:03:17 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


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