Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6DF8017A8D for ; Thu, 19 Mar 2015 23:15:39 +0000 (UTC) Received: (qmail 36109 invoked by uid 500); 19 Mar 2015 23:15:39 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 36074 invoked by uid 500); 19 Mar 2015 23:15:39 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 36059 invoked by uid 99); 19 Mar 2015 23:15:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 23:15:39 +0000 Date: Thu, 19 Mar 2015 23:15:39 +0000 (UTC) From: "Aleksandr Kovalenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-10136) Web Client Continues To Make Requests After Logout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370313#comment-14370313 ] Aleksandr Kovalenko commented on AMBARI-10136: ---------------------------------------------- +1 for the patch > Web Client Continues To Make Requests After Logout > -------------------------------------------------- > > Key: AMBARI-10136 > URL: https://issues.apache.org/jira/browse/AMBARI-10136 > 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 (v6.3.4#6332)