ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-10136) Web Client Continues To Make Requests After Logout
Date Thu, 19 Mar 2015 22:04:38 GMT


Hadoop QA commented on AMBARI-10136:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results:
Console output:

This message is automatically generated.

> Web Client Continues To Make Requests After Logout
> --------------------------------------------------
>                 Key: AMBARI-10136
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.1.0
>         Attachments: AMBARI-10136.patch
> During the provisioning of a new cluster, the web client continues to make requests after
logging out. 
> Reproduction Steps:
> 1) Create a new cluster
> 2) Deploy the cluster and watch the progress bars start
> 3) While the cluster is still being deployed, log out.
> 4) Observe that after the logout URL is invoked, there are still requests being made
to api/v1/clusters/c1/requests/
> Attaching a HAR file that shows the requests to api/v1/clusters/c1/requests/ followed
by a request to api/v1/logout, followed by more requests to api/v1/clusters/c1/requests.

This message was sent by Atlassian JIRA

View raw message