e
> >>> connectionLimitLatch and this is specifically nulled out during the
> >>> pause
> >>> phase (I suppose because it also has the function of limiting
> >>> connections),
> >>> so the getConnectionCount() method returns -1 even if there are open
I can clean up and share the patch, but let me know if you think it
should
be done differently than described above. :-)
Br, M. Thiim
Den fre. 18. nov. 2022 kl. 14.34 skrev Mark Thomas :
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed that Tomcat doesn't gracefully clos
t;>> Connection: keep-alive
> >>>
> >>> Thereby informing the client of the full 20 sec. keepalive timeout,
> >> making
> >>> it think it can keep using the connection - so the client ends up
> getting
> >>> the same error just with a
ends up getting
the same error just with a 20 second delay... In fact, the server even
accepts completely new connections during the graceful shutdown period
period.
Br, M. Thiim
Den fre. 18. nov. 2022 kl. 14.34 skrev Mark Thomas :
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed th
can keep using the connection - so the client ends up getting
> > the same error just with a 20 second delay... In fact, the server even
> > accepts completely new connections during the graceful shutdown period
> > period.
> >
> > Br, M. Thiim
> >
> > Den fre. 18
eriod.
Br, M. Thiim
Den fre. 18. nov. 2022 kl. 14.34 skrev Mark Thomas :
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed that Tomcat doesn't gracefully close
keep-alive connections. Tomcat waits for already started requests to
complete, but once those are done, Tomcat will close
> On 17/11/2022 19:39, M. Thiim wrote:
> > Hi,
> >
> > We have observed that Tomcat doesn't gracefully close
> > keep-alive connections. Tomcat waits for already started requests to
> > complete, but once those are done, Tomcat will close all connections
:
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed that Tomcat doesn't gracefully close
keep-alive connections. Tomcat waits for already started requests to
complete, but once those are done, Tomcat will close all connections
immediately, irrespective of any configured keepAli
ow if you think it should
be done differently than described above. :-)
Br, M. Thiim
Den fre. 18. nov. 2022 kl. 14.34 skrev Mark Thomas :
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed that Tomcat doesn't gracefully close
keep-alive connections. Tomcat waits for already started
ifferently than described above. :-)
Br, M. Thiim
Den fre. 18. nov. 2022 kl. 14.34 skrev Mark Thomas :
> On 17/11/2022 19:39, M. Thiim wrote:
> > Hi,
> >
> > We have observed that Tomcat doesn't gracefully close
> > keep-alive connections. Tomcat waits for already
On 17/11/2022 19:39, M. Thiim wrote:
Hi,
We have observed that Tomcat doesn't gracefully close
keep-alive connections. Tomcat waits for already started requests to
complete, but once those are done, Tomcat will close all connections
immediately, irrespective of any configured keepAliveTi
Hi,
We have observed that Tomcat doesn't gracefully close
keep-alive connections. Tomcat waits for already started requests to
complete, but once those are done, Tomcat will close all connections
immediately, irrespective of any configured keepAliveTimeout. This causes
problems for some
12 matches
Mail list logo