From users-return-267597-archive-asf-public=cust-asf.ponee.io@tomcat.apache.org Thu May 23 08:05:10 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5C5D618062F for ; Thu, 23 May 2019 10:05:10 +0200 (CEST) Received: (qmail 22954 invoked by uid 500); 23 May 2019 08:05:07 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 22940 invoked by uid 99); 23 May 2019 08:05:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 May 2019 08:05:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 78C4A180650 for ; Thu, 23 May 2019 08:05:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.8 X-Spam-Level: * X-Spam-Status: No, score=1.8 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id bu5WKIt_9LxP for ; Thu, 23 May 2019 08:05:04 +0000 (UTC) Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id D812E5F300 for ; Thu, 23 May 2019 08:05:03 +0000 (UTC) Received: by mail-lj1-f171.google.com with SMTP id z1so4573037ljb.3 for ; Thu, 23 May 2019 01:05:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=uSg1vLVIfbftSyG1FT9jRMx+pKB/NyEfcw86bdN83BE=; b=vIRRSdmwXxltb4DY9F+qh4e8MS/mx/gmxeuispyu2oVY5d7SAb4jhI60lE6B2Yn/0J Ny6+EwlkjAY/jaNhCk94rNnIFgawUVWKAVa09sGqljlFlqg4PIyqbKtyLsaXLDum7hjL F/g9C+LxnBIlrEHZivEIbrkkiyTZMudDaSs4aV2QViN6ILmLlN8m1SnK2C2PtdOXbxGF 7nWSKAUbuoTkuwxpFxG0t2GvZ2Sg2+0ZGKWe+tdk5+uiz6POFDhswTIqwTyH1nUBK5XP JNI+PydKO5gnCXUXa5Zf1LagQ1pSV3UI1FSUSThEJ+CDBOW57FC72LeMo1uBVq0OSQyu rDNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=uSg1vLVIfbftSyG1FT9jRMx+pKB/NyEfcw86bdN83BE=; b=RsX55PWTUQnHcGHZaFW8yP75w3P/zgj4vT1llcLGoYKeyRJSNkc0q4DXug17ucJN3u dvHiPPtyO2SnTwcsbqsxppfTy/E+d8PR48RQq2CzfonUUvmKqAJjFhjKngtsJiYTweR5 eW3LMz2vo0LNrw+05wyjCe1SZGX22qSDbr9JI3pbudRPHFThk0DHK4Bl2sLEHeJiZ4eD abBMTZTIleruum4ni+FTfZYGPqIX9OxqzpCMPuztXC8pdnef3zwlUWucoYnphUUYBgks bEQT//cX7rd+otz8V8g0hK++CCerkIBSRH6Vn734PjRrGyB40/2hroGrmWT5VgZRzR1/ jlhw== X-Gm-Message-State: APjAAAU3iJpMtuu3kzuzJVfpUVQ1/IvkoehEuanxrlUd9XlN8KB1B25w UD7gsvUljqH/weNDPkr4pNk9EwinEI7z585SWnUfar7JG/Y= X-Google-Smtp-Source: APXvYqyjowvqmsIV/eL/hH1jgiJZE31M8NX5T2+BYHx9KPnTBzmC7P9EfN2RDaINDEKUriCRlqGniD/9UUEYvAKCH/4= X-Received: by 2002:a2e:8709:: with SMTP id m9mr21388736lji.25.1558598696172; Thu, 23 May 2019 01:04:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tom Coudyzer Date: Thu, 23 May 2019 10:04:43 +0200 Message-ID: Subject: Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled To: Tomcat Users List Content-Type: multipart/alternative; boundary="000000000000a2056c058989892d" --000000000000a2056c058989892d Content-Type: text/plain; charset="UTF-8" Hi, We analyzed the problem further and we have set up another version which is using Tomcat 9.0.19. We don't have the issue anymore. So it looks like it's caused by something that has changed between the two versions. Based on the info I have it looks like Chrome is stalling and getting too many responses at the same time. In the meantime we activated already the access log and all files in that file are sent with status 200. So it looks like a client / browser side issue. Does this information give more information on what could be causing the problem or which parameter we should set up / change or do you still need more information? On Wed, May 22, 2019 at 5:01 PM Mark Thomas wrote: > On 22/05/2019 15:47, Tom Coudyzer wrote: > > Hi, > > > > We wanted to upgrade our application to start using HTTP/2. We added the > > necessary and we see that the browser is using HTTP/2 in the browsers' > > development tools. > > > > However since we activated it we get random CONNECTION_CLOSED 200 Errors > in > > Chrome. It's not always on the same files and sometimes there are more, > > sometimes there are less, sometimes it works. When we disable HTTP/2 > > (remove the upgradeprotocol tag) everything works fine. > > > > We are running Tomcat 9.0.20 (x64) on a Windows Server 2008 R2 server. > > > > Did we configure something incorrectly, is this an HTTP/2 issue or should > > we look at network issues on our end? > > > > If you need more information or we need to run something to be able to > > troubleshoot it better please let me know. > > > > Help is much appreciated ! > > You can try enabling debug logging if the issue is fairly easy to > reproduce. That might shed some light on what Tomcat is doing and why. > > There are also some HTTP/2 fixes due in the next set of releases that > might help. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --000000000000a2056c058989892d--