Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

No problem, glad i could be of use (although my role is minimal)

Regards,
/Tom

On Tue, May 28, 2019 at 1:44 PM Rémy Maucherat  wrote:

> On Tue, May 28, 2019 at 1:18 PM Tom Coudyzer  wrote:
>
> > Hi Mark,
> >
> > The same goes for you,  so thank you for helping to solve this and
> > providing the test build.
> > I downloaded and installed this version and it works now.
> >
> > Following tests were executed:
> >
> > - without useAsyncIO attribute
> > - with useAsyncIO="true"
> > - with useAsyncIO="false"
> >
> > In all 3 scenarios it worked correctly and no errors were reported in the
> > browser console.
> >
>
> Nice, thanks for the testing !
>
> Rémy
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Rémy Maucherat]

On Tue, May 28, 2019 at 1:18 PM Tom Coudyzer  wrote:

> Hi Mark,
>
> The same goes for you,  so thank you for helping to solve this and
> providing the test build.
> I downloaded and installed this version and it works now.
>
> Following tests were executed:
>
> - without useAsyncIO attribute
> - with useAsyncIO="true"
> - with useAsyncIO="false"
>
> In all 3 scenarios it worked correctly and no errors were reported in the
> browser console.
>

Nice, thanks for the testing !

Rémy

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi Mark,

The same goes for you,  so thank you for helping to solve this and
providing the test build.
I downloaded and installed this version and it works now.

Following tests were executed:

- without useAsyncIO attribute
- with useAsyncIO="true"
- with useAsyncIO="false"

In all 3 scenarios it worked correctly and no errors were reported in the
browser console.

Regards,
/Tom

On Tue, May 28, 2019 at 12:04 PM Mark Thomas  wrote:

> On 24/05/2019 14:07, Tom Coudyzer wrote:
> > Hi,
> >
> > No problem, if we need to test something just let me know. Will download
> > and execute a test with the new test build.
>
> Thanks Tom. Your willingness to test fixes is much appreciated.
>
> Please test the following test build (not an official release, same
> caveats as before) with both useAsyncIO="false" and useAsyncIO="true" on
> the Connector.
>
> http://people.apache.org/~markt/dev/v9.0.21-dev-003e071/
>
> Thanks,
>
> Mark
>
>
> >
> > Thanks for all the support !
> >
> > /Tom
> >
> > On Fri, May 24, 2019 at 2:59 PM Rémy Maucherat  wrote:
> >
> >> On Thu, May 23, 2019 at 10:59 PM Tom Coudyzer 
> wrote:
> >>
> >>>
> >>> Should we see this as an issue in our code which requires (for some
> >> reason)
> >>> that scripts are loaded in some sequence or is this something that
> needs
> >> to
> >>> be fixed?
> >>>
> >>
> >> No. But it would be nice if you would test another test build later.
> >>
> >> Rémy
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Mark Thomas]

On 24/05/2019 14:07, Tom Coudyzer wrote:
> Hi,
> 
> No problem, if we need to test something just let me know. Will download
> and execute a test with the new test build.

Thanks Tom. Your willingness to test fixes is much appreciated.

Please test the following test build (not an official release, same
caveats as before) with both useAsyncIO="false" and useAsyncIO="true" on
the Connector.

http://people.apache.org/~markt/dev/v9.0.21-dev-003e071/

Thanks,

Mark


> 
> Thanks for all the support !
> 
> /Tom
> 
> On Fri, May 24, 2019 at 2:59 PM Rémy Maucherat  wrote:
> 
>> On Thu, May 23, 2019 at 10:59 PM Tom Coudyzer  wrote:
>>
>>>
>>> Should we see this as an issue in our code which requires (for some
>> reason)
>>> that scripts are loaded in some sequence or is this something that needs
>> to
>>> be fixed?
>>>
>>
>> No. But it would be nice if you would test another test build later.
>>
>> Rémy
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi,

No problem, if we need to test something just let me know. Will download
and execute a test with the new test build.

Thanks for all the support !

/Tom

On Fri, May 24, 2019 at 2:59 PM Rémy Maucherat  wrote:

> On Thu, May 23, 2019 at 10:59 PM Tom Coudyzer  wrote:
>
> >
> > Should we see this as an issue in our code which requires (for some
> reason)
> > that scripts are loaded in some sequence or is this something that needs
> to
> > be fixed?
> >
>
> No. But it would be nice if you would test another test build later.
>
> Rémy
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Rémy Maucherat]

On Thu, May 23, 2019 at 10:59 PM Tom Coudyzer  wrote:

>
> Should we see this as an issue in our code which requires (for some reason)
> that scripts are loaded in some sequence or is this something that needs to
> be fixed?
>

No. But it would be nice if you would test another test build later.

Rémy

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi Rémy,

Many thanks for your tip!

I added this parameter to the Connector and now it works! So it seems that
the new async IO was causing the issue.
First feeling is that response times are a little bit lower now but still
better than HTTP/1.1

Should we see this as an issue in our code which requires (for some reason)
that scripts are loaded in some sequence or is this something that needs to
be fixed?

Tnx again for helping us to resolve this, much appreciated!

Regards,
/Tom



On Thu, May 23, 2019 at 10:04 PM Rémy Maucherat  wrote:

> On Thu, May 23, 2019 at 8:44 PM Tom Coudyzer  wrote:
>
> > Hi,
> >
> > I tested with the 9.0.21-dev version and the issue is still there.
> > I attached two screenshots on what is happening in Chrome (same behavior
> > is present in Firefox). In Internet Explorer 11 there are no errors.
> >
> > While I wait on some feedback will try to find out how I can enable the
> > logging (with more info). As I told earlier Tomcat is embedded in an
> > application and it looks something has changed to the standard logging
> > mechanism. Since I was only asked recently to have a look at this
> product I
> > need to find this out.Think we'll need this so that we can see what's
> going
> > on.
> >
> > When I need to try something or you have some ideas, just let me know.
> > Will try them out.
> >
>
> Ok, so the new async IO might be the cause of your problem, you should set
> useAsyncIO="false" on the connector.
>
> I don't know what your page is doing, but I pulled the HTTP/2 test page we
> did demo with at conferences and if I insist I can see problems.
> This is caused by the check line 1530 in Http2UpgradeHandler, the state
> being CLOSED_RX (so no window updating normally). If I comment it out, I
> see no error or problems anymore in the logs, and things work reliably. So
> maybe it's a processing ordering problem caused by async. I added some sync
> in the parser and it works too, not sure why right now.
>
> Rémy
>
>
> >
> > Thanks already!
> >
> > /Tom
> >
> >
> > On Thu, May 23, 2019 at 3:42 PM Mark Thomas  wrote:
> >
> >> On 23/05/2019 11:52, Tom Coudyzer wrote:
> >> > Hi Mark,
> >> >
> >> > Thanks for the info.
> >> >
> >> > If you say where we can download the test build we are happy to do
> that
> >> and
> >> > see if it makes any difference.
> >>
> >> http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
> >>
> >> > No problem if any (serious) issues can occur, we'll have the fire
> >> > extinguishers ready :-)
> >>
> >> Great. I just wanted you to be aware that this only a test build and is
> >> in no way an official ASF release.
> >>
> >> Let us know how you get on.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> >
> >> > Once again many thanks for your help, much appreciated!
> >> >
> >> > Regards,
> >> > Tom
> >> >
> >> > On Thu, May 23, 2019 at 11:09 AM Mark Thomas 
> wrote:
> >> >
> >> >> On 23/05/2019 09:04, Tom Coudyzer wrote:
> >> >>> 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?
> >> >>
> >> >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue
> looks
> >> >> more likely than a browser issue.
> >> >>
> >> >> If I point you towards a test build (no guarantees, use at your own
> >> >> risk, if your server catches fire don't blame me etc.) for 9.0.21
> could
> >> >> you test that as there are some HTTP/2 changes in 9.0.20 that made a
> >> >> long standing bug more likely that have been fixed in 9.0.21-dev.
> >> >>
> >> >> If you still see the issue then we can look at specific debug logging
> >> >> and/or isolated test cases.
> >> >>
> >> >> Mark
> >> >>
> >> >>
> >> >>>
> >> >>> 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 

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi Marc,

Was indeed a pity that it was not resolved but I applied the asyncIO=false
attribute to the Connector as Rémy suggested and it works now. So that's
good news. Just asked him if this is an issue on our (code) side or if this
is something that needs to be looked into/fixed.

Ok, for the attachments, did not know if they would be accepted or not.
For your reference you can find the screenshots here to see what's going on
in the browser with the ERR_CONNECTION_CLOSED

https://pasteboard.co/Ig4O8SZ.png
https://pasteboard.co/Ig4OlUE.png

I activated this logging but nothing seems to happen, so will need to find
out what the original developers of this application did to "disable" this.

As always, many thanks for your help!

Regards,
/Tom

On Thu, May 23, 2019 at 10:00 PM Mark Thomas  wrote:

> On 23/05/2019 19:37, Tom Coudyzer wrote:
> > Hi,
> >
> > I tested with the 9.0.21-dev version and the issue is still there.
>
> Drat.
>
> > I attached two screenshots on what is happening in Chrome (same behavior
> > is present in Firefox). In Internet Explorer 11 there are no errors.
>
> Attachments are blocked on this list. Can you either send them to me
> directly or post them somewhere and provide a link please?
>
> > While I wait on some feedback will try to find out how I can enable the
> > logging (with more info).
>
> In logging.properties
> org.apache.coyote.http2.level = FINE
>
> It should already be there but commented out.
>
> You will get a LOT of data.
>
> > As I told earlier Tomcat is embedded in an
> > application and it looks something has changed to the standard logging
> > mechanism.
>
> Ah. That might make it a bit trickier. Hopefully the info above will help.
>
> Mark
>
>
> > Since I was only asked recently to have a look at this
> > product I need to find this out.Think we'll need this so that we can see
> > what's going on.
> >
> > When I need to try something or you have some ideas, just let me know.
> > Will try them out.
> >
> > Thanks already!
> >
> > /Tom
> >
> >
> > On Thu, May 23, 2019 at 3:42 PM Mark Thomas  > > wrote:
> >
> > On 23/05/2019 11:52, Tom Coudyzer wrote:
> > > Hi Mark,
> > >
> > > Thanks for the info.
> > >
> > > If you say where we can download the test build we are happy to do
> > that and
> > > see if it makes any difference.
> >
> > http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
> >
> > > No problem if any (serious) issues can occur, we'll have the fire
> > > extinguishers ready :-)
> >
> > Great. I just wanted you to be aware that this only a test build and
> is
> > in no way an official ASF release.
> >
> > Let us know how you get on.
> >
> > Thanks,
> >
> > Mark
> >
> >
> > >
> > > Once again many thanks for your help, much appreciated!
> > >
> > > Regards,
> > > Tom
> > >
> > > On Thu, May 23, 2019 at 11:09 AM Mark Thomas  > > wrote:
> > >
> > >> On 23/05/2019 09:04, Tom Coudyzer wrote:
> > >>> 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?
> > >>
> > >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue
> > looks
> > >> more likely than a browser issue.
> > >>
> > >> If I point you towards a test build (no guarantees, use at your
> own
> > >> risk, if your server catches fire don't blame me etc.) for 9.0.21
> > could
> > >> you test that as there are some HTTP/2 changes in 9.0.20 that
> made a
> > >> long standing bug more likely that have been fixed in 9.0.21-dev.
> > >>
> > >> If you still see the issue then we can look at specific debug
> logging
> > >> and/or isolated test cases.
> > >>
> > >> Mark
> > >>
> > >>
> > >>>
> > >>> 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 

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Rémy Maucherat]

On Thu, May 23, 2019 at 8:44 PM Tom Coudyzer  wrote:

> Hi,
>
> I tested with the 9.0.21-dev version and the issue is still there.
> I attached two screenshots on what is happening in Chrome (same behavior
> is present in Firefox). In Internet Explorer 11 there are no errors.
>
> While I wait on some feedback will try to find out how I can enable the
> logging (with more info). As I told earlier Tomcat is embedded in an
> application and it looks something has changed to the standard logging
> mechanism. Since I was only asked recently to have a look at this product I
> need to find this out.Think we'll need this so that we can see what's going
> on.
>
> When I need to try something or you have some ideas, just let me know.
> Will try them out.
>

Ok, so the new async IO might be the cause of your problem, you should set
useAsyncIO="false" on the connector.

I don't know what your page is doing, but I pulled the HTTP/2 test page we
did demo with at conferences and if I insist I can see problems.
This is caused by the check line 1530 in Http2UpgradeHandler, the state
being CLOSED_RX (so no window updating normally). If I comment it out, I
see no error or problems anymore in the logs, and things work reliably. So
maybe it's a processing ordering problem caused by async. I added some sync
in the parser and it works too, not sure why right now.

Rémy


>
> Thanks already!
>
> /Tom
>
>
> On Thu, May 23, 2019 at 3:42 PM Mark Thomas  wrote:
>
>> On 23/05/2019 11:52, Tom Coudyzer wrote:
>> > Hi Mark,
>> >
>> > Thanks for the info.
>> >
>> > If you say where we can download the test build we are happy to do that
>> and
>> > see if it makes any difference.
>>
>> http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
>>
>> > No problem if any (serious) issues can occur, we'll have the fire
>> > extinguishers ready :-)
>>
>> Great. I just wanted you to be aware that this only a test build and is
>> in no way an official ASF release.
>>
>> Let us know how you get on.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> >
>> > Once again many thanks for your help, much appreciated!
>> >
>> > Regards,
>> > Tom
>> >
>> > On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:
>> >
>> >> On 23/05/2019 09:04, Tom Coudyzer wrote:
>> >>> 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?
>> >>
>> >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
>> >> more likely than a browser issue.
>> >>
>> >> If I point you towards a test build (no guarantees, use at your own
>> >> risk, if your server catches fire don't blame me etc.) for 9.0.21 could
>> >> you test that as there are some HTTP/2 changes in 9.0.20 that made a
>> >> long standing bug more likely that have been fixed in 9.0.21-dev.
>> >>
>> >> If you still see the issue then we can look at specific debug logging
>> >> and/or isolated test cases.
>> >>
>> >> Mark
>> >>
>> >>
>> >>>
>> >>> 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
>> 
>>  

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Mark Thomas]

On 23/05/2019 19:37, Tom Coudyzer wrote:
> Hi, 
> 
> I tested with the 9.0.21-dev version and the issue is still there.

Drat.
 
> I attached two screenshots on what is happening in Chrome (same behavior
> is present in Firefox). In Internet Explorer 11 there are no errors.

Attachments are blocked on this list. Can you either send them to me
directly or post them somewhere and provide a link please?

> While I wait on some feedback will try to find out how I can enable the
> logging (with more info).

In logging.properties
org.apache.coyote.http2.level = FINE

It should already be there but commented out.

You will get a LOT of data.

> As I told earlier Tomcat is embedded in an
> application and it looks something has changed to the standard logging
> mechanism.

Ah. That might make it a bit trickier. Hopefully the info above will help.

Mark


> Since I was only asked recently to have a look at this
> product I need to find this out.Think we'll need this so that we can see
> what's going on.
> 
> When I need to try something or you have some ideas, just let me know.
> Will try them out.
> 
> Thanks already!
> 
> /Tom
> 
> 
> On Thu, May 23, 2019 at 3:42 PM Mark Thomas  > wrote:
> 
> On 23/05/2019 11:52, Tom Coudyzer wrote:
> > Hi Mark,
> >
> > Thanks for the info.
> >
> > If you say where we can download the test build we are happy to do
> that and
> > see if it makes any difference.
> 
> http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
> 
> > No problem if any (serious) issues can occur, we'll have the fire
> > extinguishers ready :-)
> 
> Great. I just wanted you to be aware that this only a test build and is
> in no way an official ASF release.
> 
> Let us know how you get on.
> 
> Thanks,
> 
> Mark
> 
> 
> >
> > Once again many thanks for your help, much appreciated!
> >
> > Regards,
> > Tom
> >
> > On Thu, May 23, 2019 at 11:09 AM Mark Thomas  > wrote:
> >
> >> On 23/05/2019 09:04, Tom Coudyzer wrote:
> >>> 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?
> >>
> >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue
> looks
> >> more likely than a browser issue.
> >>
> >> If I point you towards a test build (no guarantees, use at your own
> >> risk, if your server catches fire don't blame me etc.) for 9.0.21
> could
> >> you test that as there are some HTTP/2 changes in 9.0.20 that made a
> >> long standing bug more likely that have been fixed in 9.0.21-dev.
> >>
> >> If you still see the issue then we can look at specific debug logging
> >> and/or isolated test cases.
> >>
> >> Mark
> >>
> >>
> >>>
> >>> 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
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi,

I tested with the 9.0.21-dev version and the issue is still there.
I attached two screenshots on what is happening in Chrome (same behavior is
present in Firefox). In Internet Explorer 11 there are no errors.

While I wait on some feedback will try to find out how I can enable the
logging (with more info). As I told earlier Tomcat is embedded in an
application and it looks something has changed to the standard logging
mechanism. Since I was only asked recently to have a look at this product I
need to find this out.Think we'll need this so that we can see what's going
on.

When I need to try something or you have some ideas, just let me know. Will
try them out.

Thanks already!

/Tom


On Thu, May 23, 2019 at 3:42 PM Mark Thomas  wrote:

> On 23/05/2019 11:52, Tom Coudyzer wrote:
> > Hi Mark,
> >
> > Thanks for the info.
> >
> > If you say where we can download the test build we are happy to do that
> and
> > see if it makes any difference.
>
> http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
>
> > No problem if any (serious) issues can occur, we'll have the fire
> > extinguishers ready :-)
>
> Great. I just wanted you to be aware that this only a test build and is
> in no way an official ASF release.
>
> Let us know how you get on.
>
> Thanks,
>
> Mark
>
>
> >
> > Once again many thanks for your help, much appreciated!
> >
> > Regards,
> > Tom
> >
> > On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:
> >
> >> On 23/05/2019 09:04, Tom Coudyzer wrote:
> >>> 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?
> >>
> >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
> >> more likely than a browser issue.
> >>
> >> If I point you towards a test build (no guarantees, use at your own
> >> risk, if your server catches fire don't blame me etc.) for 9.0.21 could
> >> you test that as there are some HTTP/2 changes in 9.0.20 that made a
> >> long standing bug more likely that have been fixed in 9.0.21-dev.
> >>
> >> If you still see the issue then we can look at specific debug logging
> >> and/or isolated test cases.
> >>
> >> Mark
> >>
> >>
> >>>
> >>> 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-unsubscr...@tomcat.apache.org
>  For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: 

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Thanks Mark.

We will test and report back.

/Tom

On Thu, May 23, 2019 at 3:42 PM Mark Thomas  wrote:

> On 23/05/2019 11:52, Tom Coudyzer wrote:
> > Hi Mark,
> >
> > Thanks for the info.
> >
> > If you say where we can download the test build we are happy to do that
> and
> > see if it makes any difference.
>
> http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/
>
> > No problem if any (serious) issues can occur, we'll have the fire
> > extinguishers ready :-)
>
> Great. I just wanted you to be aware that this only a test build and is
> in no way an official ASF release.
>
> Let us know how you get on.
>
> Thanks,
>
> Mark
>
>
> >
> > Once again many thanks for your help, much appreciated!
> >
> > Regards,
> > Tom
> >
> > On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:
> >
> >> On 23/05/2019 09:04, Tom Coudyzer wrote:
> >>> 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?
> >>
> >> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
> >> more likely than a browser issue.
> >>
> >> If I point you towards a test build (no guarantees, use at your own
> >> risk, if your server catches fire don't blame me etc.) for 9.0.21 could
> >> you test that as there are some HTTP/2 changes in 9.0.20 that made a
> >> long standing bug more likely that have been fixed in 9.0.21-dev.
> >>
> >> If you still see the issue then we can look at specific debug logging
> >> and/or isolated test cases.
> >>
> >> Mark
> >>
> >>
> >>>
> >>> 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-unsubscr...@tomcat.apache.org
>  For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Mark Thomas]

On 23/05/2019 11:52, Tom Coudyzer wrote:
> Hi Mark,
> 
> Thanks for the info.
> 
> If you say where we can download the test build we are happy to do that and
> see if it makes any difference.

http://people.apache.org/~markt/dev/v9.0.21-dev-d6d3b31/

> No problem if any (serious) issues can occur, we'll have the fire
> extinguishers ready :-)

Great. I just wanted you to be aware that this only a test build and is
in no way an official ASF release.

Let us know how you get on.

Thanks,

Mark


> 
> Once again many thanks for your help, much appreciated!
> 
> Regards,
> Tom
> 
> On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:
> 
>> On 23/05/2019 09:04, Tom Coudyzer wrote:
>>> 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?
>>
>> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
>> more likely than a browser issue.
>>
>> If I point you towards a test build (no guarantees, use at your own
>> risk, if your server catches fire don't blame me etc.) for 9.0.21 could
>> you test that as there are some HTTP/2 changes in 9.0.20 that made a
>> long standing bug more likely that have been fixed in 9.0.21-dev.
>>
>> If you still see the issue then we can look at specific debug logging
>> and/or isolated test cases.
>>
>> Mark
>>
>>
>>>
>>> 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-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Rémy Maucherat]

On Thu, May 23, 2019 at 12:53 PM Tom Coudyzer  wrote:

> Hi Mark,
>
> Thanks for the info.
>
> If you say where we can download the test build we are happy to do that and
> see if it makes any difference.
> No problem if any (serious) issues can occur, we'll have the fire
> extinguishers ready :-)
>
> Once again many thanks for your help, much appreciated!
>

Tomcat 9.0.20 has known HTTP/2 issues:
- The new async NIO code still had some random bugs that caused connection
errors
- The timeout issue which caused the connection to be often closed once it
hit its window size

The current fixed Tomcat looks ok to me with chrome, but if the problem is
rare it would be more difficult to reproduce.

Rémy


>
> Regards,
> Tom
>
> On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:
>
> > On 23/05/2019 09:04, Tom Coudyzer wrote:
> > > 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?
> >
> > Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
> > more likely than a browser issue.
> >
> > If I point you towards a test build (no guarantees, use at your own
> > risk, if your server catches fire don't blame me etc.) for 9.0.21 could
> > you test that as there are some HTTP/2 changes in 9.0.20 that made a
> > long standing bug more likely that have been fixed in 9.0.21-dev.
> >
> > If you still see the issue then we can look at specific debug logging
> > and/or isolated test cases.
> >
> > Mark
> >
> >
> > >
> > > 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-unsubscr...@tomcat.apache.org
> > >> For additional commands, e-mail: users-h...@tomcat.apache.org
> > >>
> > >>
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Hi Mark,

Thanks for the info.

If you say where we can download the test build we are happy to do that and
see if it makes any difference.
No problem if any (serious) issues can occur, we'll have the fire
extinguishers ready :-)

Once again many thanks for your help, much appreciated!

Regards,
Tom

On Thu, May 23, 2019 at 11:09 AM Mark Thomas  wrote:

> On 23/05/2019 09:04, Tom Coudyzer wrote:
> > 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?
>
> Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
> more likely than a browser issue.
>
> If I point you towards a test build (no guarantees, use at your own
> risk, if your server catches fire don't blame me etc.) for 9.0.21 could
> you test that as there are some HTTP/2 changes in 9.0.20 that made a
> long standing bug more likely that have been fixed in 9.0.21-dev.
>
> If you still see the issue then we can look at specific debug logging
> and/or isolated test cases.
>
> Mark
>
>
> >
> > 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-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Mark Thomas]

On 23/05/2019 09:04, Tom Coudyzer wrote:
> 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?

Given the issue appears between 9.0.19 and 9.0.20 a Tomcat issue looks
more likely than a browser issue.

If I point you towards a test build (no guarantees, use at your own
risk, if your server catches fire don't blame me etc.) for 9.0.21 could
you test that as there are some HTTP/2 changes in 9.0.20 that made a
long standing bug more likely that have been fixed in 9.0.21-dev.

If you still see the issue then we can look at specific debug logging
and/or isolated test cases.

Mark


> 
> 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-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

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-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

Thanks Mark,

Will have a look to enable debug mode. Probably need to do some
investigation as Tomcat is embedded in the full product and some probably
some standard logging configuration is changed.

Tom

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-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Mark Thomas]

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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

CONNECTION_CLOSED 200 Error with HTTP/2 Enabled

[Tom Coudyzer]

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 !

Regards,
Tom