glassfish
  1. glassfish
  2. GLASSFISH-16782

status not available for http load balancers

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: load_balancer
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          srinik76 created issue -
          srinik76 made changes -
          Field Original Value New Value
          Link This issue blocks GLASSFISH-16763 [ GLASSFISH-16763 ]
          Hide
          srinik76 added a comment -

          Fix required for 3.1.1

          Show
          srinik76 added a comment - Fix required for 3.1.1
          srinik76 made changes -
          Fix Version/s 3.1.1 [ 14740 ]
          srinik76 made changes -
          Tags 3_1_
          Hide
          kshitiz_saxena added a comment -

          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.

          Show
          kshitiz_saxena added a comment - 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.
          kshitiz_saxena made changes -
          Fix Version/s 3.1.1 [ 14740 ]
          Tags 3_1_ 3_1_ 3_1-next
          kshitiz_saxena made changes -
          Tags 3_1_ 3_1-next 3_1-next 3_1_ 3_1_1-exclude
          kshitiz_saxena made changes -
          Tags 3_1-next 3_1_ 3_1_1-exclude 3_1-next 3_1_ 3_1_1-exclude 3_1_1-scrubbed
          kshitiz_saxena made changes -
          Tags 3_1-next 3_1_ 3_1_1-exclude 3_1_1-scrubbed 3_1-next 3_1_ 3_1_1-exclude 3_1_1-next 3_1_1-scrubbed
          kshitiz_saxena made changes -
          Tags 3_1-next 3_1_ 3_1_1-exclude 3_1_1-next 3_1_1-scrubbed 3_1-next 3_1_ 3_1_1-exclude 3_1_1-next 3_1_1-scrubbed 3_1_2-exclude

            People

            • Assignee:
              kshitiz_saxena
              Reporter:
              srinik76
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: