Doug,
On 1/12/23 15:51, Doug Whitfield wrote:
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"
>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
Doug,
There were a couple of questions in my original response it would be
useful to get answers to.
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
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
a non-Redisson-based
segmented cluster, such as one using Tomcat's BackupManager?
-chris
From: Mark Thomas
Date: Monday, January 9, 2023 at 12:12
To: users@tomcat.apache.org
Subject: Re: Question about Redisson
Given the disparaging comments OpenLogic makes about obtaining support
for ope
ink>
From: Mark Thomas
Date: Monday, January 9, 2023 at 12:12
To: users@tomcat.apache.org
Subject: Re: Question about Redisson
Given the disparaging comments OpenLogic makes about obtaining support
for open source projects from a community forum, it is more than a tad
ironic to see an Ope
Given the disparaging comments OpenLogic makes about obtaining support
for open source projects from a community forum, it is more than a tad
ironic to see an OpenLogic Enterprise Architect asking for help here.
I suggest that OpenLogic replace the text on their home page with
something
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.
