[GLASSFISH-19722] module-monitoring-levels should not include cloud related attributes Created: 23/Feb/13  Updated: 11/Sep/14

Status: Open
Project: glassfish
Component/s: monitoring
Affects Version/s: 4.0_b77
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: Anissa Lam Assignee: srinik76
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: console

 Description   

Console's Monitoring Service page list out the attributes of module-monitoring-levels and allow user to set each one to be OFF/LOW/HIGH.
The attributes related to cloud such as cloud, cloud-account-manager, cloud-elasticity, cloud-orchestrator, shouldn't be included nor returned for GlassFish.

%~ 16) asadmin get configs.config.server-config.monitoring-service.module-monitoring-levels
configs.config.server-config.monitoring-service.module-monitoring-levels.cloud=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.cloud-account-manager=HIGH
configs.config.server-config.monitoring-service.module-monitoring-levels.cloud-elasticity=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.cloud-orchestrator=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.cloud-virt-assembly-service=HIGH
configs.config.server-config.monitoring-service.module-monitoring-levels.connector-connection-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.connector-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.deployment=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.ejb-container=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.http-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jdbc-connection-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jersey=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jms-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jpa=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.jvm=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.orb=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.security=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.thread-pool=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.transaction-service=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.web-container=OFF
configs.config.server-config.monitoring-service.module-monitoring-levels.web-services-container=OFF
Command get executed successfully.

cloud related attributes should be removed from GlassFish 4.0



 Comments   
Comment by Byron Nevins [ 24/Feb/13 ]

This was done by Suma and Srini last May

Ref:
com.sun.enterprise.config.serverbeans.ModuleMonitoringLevels

Comment by Anissa Lam [ 08/Mar/13 ]

Change the fix version to b82, MS7.
MS7 is the HCF day, 3/25.

Comment by srinik76 [ 21/Mar/13 ]

There is already a HK2 RFE raised to address this issue. (http://java.net/jira/browse/HK2-23)
Also there is a wiki page which lists outs the information this issue.

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Nucleus+Cleanup+-+Monitoring

To fix the current issue we need to fix the above blocking issue.

Comments from Nazrul...

We should take this to a CCC meeting if we are unable to fix the HK2 RFE.

Chris/Masoud: We should explore why we are not able to fix HK2 RFE. Please schedule a meeting with HK2 team first (John Wells, Mahesh, Larry F, Tom Snyder).
After that, depending on the result, please schedule a CCC meeting and include Bill, Paul Davies, Sudipa and folks we need from Dev (Tom, Mahesh, John Wells).

Thanks.

Comment by Anissa Lam [ 02/Apr/13 ]

I have added a filter in the GUI code to filter out any modules that starts with "cloud".
Log Message:
------------
work around for GLASSFISH-19722. hide cloud modules for monitoring level screen.

Revisions:
----------
61083

Modified Paths:
---------------
trunk/main/appserver/admingui/common/src/main/java/org/glassfish/admingui/common/handlers/MonitoringHandlers.java

When this bug is fixed, the workaround should be removed as it is not needed.

Comment by Anissa Lam [ 08/Apr/13 ]

Since i have put in the workaround for the console by filtering out the cloud* container name, the actual fix of this bug can be deferred to after 4.0.
I am changing the target to 4.1.

Comment by Anissa Lam [ 26/Apr/13 ]

I saw that Srini added "4_0-release-notes" to the tag.
Do we really need to release note this, how does the release note help our users ?
With the work around, user will not see the cloud related monitoring level in the console, they will only see it exists by using CLI get and then set it.
Setting it doesn't give any error and user will not notice any problem as they won't see cloud related monitoring anyway.

I feel that adding this to the release note is just going to prevent user to easily see issues that they should be aware of.

Comment by srinik76 [ 29/Apr/13 ]

As per anissa's comment i am removing the tag on 4_0_release_notes





[GLASSFISH-17936] Enable secure admin text fields to not have default values Created: 08/Dec/11  Updated: 08/Dec/11

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: srinik76 Assignee: srinik76
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Enable Secure admin page text fields does not contain default values






[GLASSFISH-18156] Load defaults in Edit Health checker of LB Config removes URL value from '/' to '' Created: 09/Jan/12  Updated: 10/Jan/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1.2_b16
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: arunkumar_s Assignee: srinik76
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OEL


Tags: 312_qa

 Description   

Steps:

1) Login into glassfish and create a LB config with some target.
2) Open the LB and Edit Health checker under target tab of the cluster/instance
3) Click Load Defaults

The Default value of the URL field in Health checker section changes from '/' to ''



 Comments   
Comment by Anissa Lam [ 09/Jan/12 ]

There is no default value for the url attribute in HealthChecker config.
However, the console convention is that if there is no default value, that field should stay the same, not being emptied out.
So, GUI code should fix that.

However, if you think this field should have "/" as default value, you need to file a bug against backend.

Comment by Anissa Lam [ 10/Jan/12 ]

Given the fact that there is really no default value for this attribute, and the fact that there is only 3 attributes show on the screen, that user will very easily notice this change, I am lowering this to P4.
Unless Srini can find an easy fix, get this reviewed and approved by Joe before the HCF tonight, we will look into this in next v3 release.





[GLASSFISH-18279] HTTP 500 error when LB name contains Hash (#) Created: 31/Jan/12  Updated: 31/Jan/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1.2_b19
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: arunkumar_s Assignee: srinik76
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OEL


Tags: 312_qa

 Description   

Steps

Login Admin console and create a LB with name contains #

When trying to create a LB config with invalid characters, Error message comes as "Invalid load-balancer name. The name must start with a letter, number or underscore and may contain only letters, numbers, and these characters: hyphen, period, underscore, hash and semicolon." as expected

If we create a LB with HASH(#) HTTP 500 error message throws up.



 Comments   
Comment by arunkumar_s [ 31/Jan/12 ]

Same issue happens with semi-colon

Comment by Anissa Lam [ 31/Jan/12 ]

Negative testing, lower the priority, will look at this in next release.





Generated at Fri Mar 06 21:59:58 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.