On Fri, Mar 1, 2019 at 4:46 AM Mark Thomas wrote:
>
> On 28/02/2019 20:29, Austin Bookhart wrote:
> > Hi,
> >
> > I have a question regarding an asynchronous websocket implementation
> > we have in our application. We have run into issues where on a rare
> > occasion the websocket endpoint will
> From what I see in the test a STREAM_REFUSED is returned when a the
maxConcurrentStream is set to one. Yet I'd like to understand how this
value is changed internally. I think >the only difference with my code is
the call to the method doHttpUpgrade() which seems to send a GET for
upgrade. Does
On 28/02/2019 20:29, Austin Bookhart wrote:
> Hi,
>
> I have a question regarding an asynchronous websocket implementation
> we have in our application. We have run into issues where on a rare
> occasion the websocket endpoint will become unusable due to what seems
> to be a thread holding onto
On 27/02/2019 08:37, Helena Carbajo wrote:
>>> See
>>> https://github.com/apache/tomcat/blob/8.5.x/test/org/apache/coyote/http2/TestHttp2Section_5_1.java#L174
>
> From what I see in the test a STREAM_REFUSED is returned when a the
> maxConcurrentStream is set to one. Yet I'd like to understand
On Thu, 28 Feb 2019 at 21:29, Austin Bookhart <
austin.bookh...@hannonhill.com> wrote:
> Hi,
>
> I have a question regarding an asynchronous websocket implementation
> we have in our application. We have run into issues where on a rare
> occasion the websocket endpoint will become unusable due to
