On 03/04/2025 05:34, Tim N wrote:
That should have been
Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
It suggests that the JasperInitializer was not trigger on start. If not
a packaging issu
On 28/03/2025 09:08, Rose Mary P T wrote:
Hi Mark,
Thank you for the confirmation.
As per your suggestion, I have modified the deployed application so that it no
longer spawns any threads but instead executes a few calls.
Please clarify what you mean by "executes a few calls".
Additionally,
For a long time up to the latest version 11 documentation, there has been a
recommended maximum limit of 4 nodes per cluster.
https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html
"This works great for smaller clusters, but we don't recommend it for
larger clusters — more than 4 nodes or so
Hi Tim,
If you have an HTTP load balancer that supports "sticky sessions", you can have
a cluster of as many Tomcat instances as you like as backend, without having to
rely on any clustering feature of Tomcat.
Yours,
Reg
> Gesendet: Freitag, den 04.04.2025 um 02:57 Uhr
> Von: "Tim N"
> An: "
> On 2025 Apr 3, at 19:57, Tim N wrote:
>
> For a long time up to the latest version 11 documentation, there has been a
> recommended maximum limit of 4 nodes per cluster.
>
> https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html
> "This works great for smaller clusters, but we don't re
HI Mark,
Thanks for your response.
I would like to seek your guidance regarding an issue I am encountering with my
current Tomcat setup. Specifically, your recent suggestions appear to
contradict my existing configuration. Could you kindly confirm whether the
following executor and connector s
Lei,
On 4/3/25 3:37 AM, 2428694096 wrote:
It is a Windows Server running on a laptop.
How did you install Tomcat?
-chris
发件人：Christopher Schultz
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additiona
