Hi folks,
This feature was added in 9.0.90:
The system property org.apache.catalina.connector.RECYCLE_FACADES will now
default to true if not specified, which will in turn set the default value for
the discardFacades connector attribute, thus causing facade objects to be
discarded by default. (
Hi Folks,
On the left sidebar of the website the download is for “Tomcat 10” while the
Documentation is for “Tomcat 10.1”. Now, between Download and Documentation
things are consistent.
I don’t think this is strictly speaking wrong, but I don’t see any good reason
for it and I do think it is a
>Also, Chris's suggesiton to look at
>org.apache.catalina.connector.RECYCLE_FACADES is a good first step. Note
> that the value you need for that may not be what you expect. It needs to
> be "true" whereas I read the name and think it should be "false" to
> disable recycling.
Thanks for coming
First off, thanks for the link. I’m bringing this up with my manager who is
much more likely to be able to make some headway with the marketing folks.
There’s surely a marketing friendly way to say “Pay for SLA”.
> Are you able to reproduce the same problem with a non-Redisson-based
> segmented
d in-line below).
On 09/01/2023 16:55, Doug Whitfield wrote:
> Hi Tomcat Community,
>
> We are seeing and issue that manifests as a cross session “bleeding”
> scenario. The issue is this:
>
> 1. User A make a new request and the request goes to pod A and gets Session1
> 2. Use
Hi Tomcat Community,
We are seeing and issue that manifests as a cross session “bleeding” scenario.
The issue is this:
1. User A make a new request and the request goes to pod A and gets Session1
2. User A's next request then gets redirected to pod B. The request is
processed using Session1
3.
want to understand the log sample:
Time: 2022-01-12 03:44:42.895, Level: FINE, Logger:
org.apache.coyote.http2.Http2Parser
org.apache.coyote.http2.Http2Parser swallow
- Connection [54], Stream [2076417], Swallowed [0] bytes
Best Regards,
--
Doug Whitfield | Enterprise Architect,
OpenLogic<ht
> It exists in all 8.5.x, 9.0.x and 10.0.x versions. It has been there
> since the beginning of HTTP/2 support.
Based on our testing the issue was introduced in 9.0.19 and 8.5.55 (we haven’t
done any testing on the 10.x branch), which is slightly after the beginning of
HTTP/2 support. I don’t
>I am working on a fix which I expect to be in the releases due out in ~1
> month's time.
Thanks Mark! Is there any chance of a patch being available before then that we
might be able to backport locally?
This e-mail may contain information that is privileged or confidential. If you
are not t
-Original Message-
From: Mark Thomas
Sent: Wednesday, March 10, 2021 6:28 PM
To: users@tomcat.apache.org
Subject: Re: Embedded Tomcat 9.0.43 : WINDOW_UPDATE not sent when receiving
http2 requests over unknown url
On 10/03/2021 05:26, Arshiya Shariff wrote:
> Hi All,
> We are using embedd
Regarding the email thread with this title: “Embedded Tomcat 9.0.43 :
WINDOW_UPDATE not sent when receiving http2 requests over unknown url”
That looks exactly like our issue, but with slightly different numbers.
From: Doug Whitfield
Date: Tuesday, March 9, 2021 at 4:02 PM
To: users
what log level? There wasn’t
anything obviously useful at FINER.
Please let me know if there is any additional information that would be useful.
Best Regards,
--
Doug Whitfield | Enterprise Architect,
OpenLogic<https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outlook-
12 matches
Mail list logo
