[GLASSFISH-16782] status not available for http load balancers Created: 02/Jun/11  Updated: 21/Oct/11

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

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

Issue Links:
blocks GLASSFISH-16763 Porting Load Balancer Console Pages f... Closed
Tags: 3_1-next, 3_1_, 3_1_1-exclude, 3_1_1-next, 3_1_1-scrubbed, 3_1_2-exclude


In v2.1.1, while listing http load balancers table contains data (name,target,status)

status is found with the following code

LoadBalancer lb = AMXUtil.getDomainRoot().getLoadBalancerMap().get(key);
if( lb != null)

{ status = GuiUtil.getMessage(lb.isApplyChangeRequired()? "loadBalancer.needApply" : "loadBalancer.upToDate"); }

In v3, to find status what is the call for lb.isApplyChangeRequired(). If back end call is there, we need to create rest api conversion for this.

Comment by srinik76 [ 06/Jun/11 ]

Fix required for 3.1.1

Comment by kshitiz_saxena [ 07/Jun/11 ]

This issue requires some support implementation to detect changes in the load-balancer xml. This implementation must detect changes to cluster, instance, application, loadbalancer config etc. There is significant amount of work involved to achieve it, and cannot be fixed within timeline for 3.1.1. This issue will be taken up post 3.1.1.

In GUI we can remove column showing apply-changes status. It is already documented that auto-detection of load-balancer xml does not exist in 3.1 and will continue in 3.1.1 as well.

Generated at Fri Nov 27 06:31:04 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.