[GLASSFISH-16040] ReleaseNotes: document Restar Required issues Created: 17/Feb/11  Updated: 08/Jul/11  Resolved: 18/Mar/11

Status: Closed
Project: glassfish
Component/s: docs
Affects Version/s: 3.1_b43
Fix Version/s: None

Type: Bug Priority: Major
Reporter: lidiam Assignee: Scott Fordin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-release-note-added, 3_1-release-notes

 Description   

This is an umbrella bug for documenting numerous issues with Restart Required. Please find the details in the following query:

http://java.net/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10358

Each bug in the query should be documented in Release Notes for 3.1.



 Comments   
Comment by Scott Fordin [ 03/Mar/11 ]

Added issue to 3.1 Release Notes.

Comment by Anissa Lam [ 14/Mar/11 ]

I am re-opening this issue so that the next doc refresh can have the correct summary.
Currently, it says:

"Description
There are a number of functions in that you can perform through the GlassFish Server
Administration Console. These functions require a server restart, but the Administration
Console does not correctly convey this."

This is not quite correct. It is saying that the Admin Console does not show the correct information to user, when in fact, the information that console shown is correct. It is that the backend or each of the components in the bug list doesn't specify that restart is required.
In order word, even if user is using CLI to look at the status, eg. list-domains or list-instances to check if instance need restart, they will see the wrong information.

So, i think the wording should be changed to reflect the issue more accurately.

Comment by Scott Fordin [ 18/Mar/11 ]

Reworded issue description. Added ulinks to umbrella issues.

Comment by Scott Fordin [ 24/Mar/11 ]

Added "release note added" tag.

Comment by lidiam [ 08/Jul/11 ]

Verified in Release Notes for 3.1 release.

Generated at Thu Sep 01 03:40:08 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.