> OK, that looks like clients with a connection timeout of 5s.
Correct. I think I forgot to mention, that I set the connection timeout of the
curl instances to 5s. I didn't set the max timeout
> >> Connection refusal is entirely under the control of the OS and will
> >> be driven largely by the a
Hi Chris,
Thanks for your email. Below are replies to your questions:
1. Did you upgrade anything recently (like Java VM)?
[YJ] To support Linux 8, only Postgres was upgraded from version 9.3 to 9.6.
2. What is error you are seeing? A full stack trace would be helpful.
[YJ] The application error
Hi Mark,
I try to get contributors from svn side with `svn log --quiet -v
http://svn.apache.org/repos/asf/tomcat | grep "^r"` and get 100
contributors in total. After removing duplicates with git, right now we
have 95 contributors till 2012 and ~150 till now (compared to 20/90 and
10/60 before).
(
Hi Mark,
I try to get contributors from svn side with `svn log --quiet -v
http://svn.apache.org/repos/asf/tomcat | grep "^r"` and get 100
contributors in total. After removing duplicates with git, right now we
have 95 contributors till 2012 and ~150 till now (compared to 20/90 and
10/60 before).
(
Environment:
OS: CentOS 7
Apache: apache-tomcat-8.5.65
Java: jdk1.8.0_281
Greetings,
I recently enabled SSL on my Tomcat server HTTP connectors. Something odd
is happening. After some undetermined amount of time the connector stops
responding appropriately to requests. My browser returns the foll
Hi all,
I was just notified about some mess going on with Freenode which has
seemingly resulted in a mass exodus of users from the freenode servers.
There are some updates available at
https://gist.github.com/joepie91/df80d8d36cd9d1bde46ba018af497409/ which
make it seem like we should no longer po
On 19/05/2021 17:37, Robert Hicks wrote:
Is that the "same" security manager we flip on for Tomcat or just an
unfortunate naming coincidence?
It is the same one.
If you need the security manager I'd expect, based on typical lifetimes
of Tomcat major versions, that you'd have a supported versi
On 19/05/2021 15:50, Chris Cheshire wrote:
Tomcat 9.0.45 - is there a way to reload the config for the rewrite valve at
runtime without reloading the web app entirely? JMX operation perhaps?
Nor cleanly, no.
You stop and start the Valve via JMX but you might see odd redirects
while that is h
Is that the "same" security manager we flip on for Tomcat or just an
unfortunate naming coincidence?
--
Bob
Tomcat 9.0.45 - is there a way to reload the config for the rewrite valve at
runtime without reloading the web app entirely? JMX operation perhaps?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional comma
On 19/05/2021 13:32, Paul P Wolf wrote:
So we have:
maxThreads=4
maxConnections=10
acceptCount=20
The processing time of each request is 10s (thanks to a 10s sleep, which blocks
the Thread).
So here is what I see instead (note I don't guess the response time, but do
actually see/measur
sorry, my message was misformated, so here again with hopefully better
formatting:
> The clients timeout because they spend more than timeout in the
> acceptCount/backlog queue waiting for Tomcat to call Socket.accept()
Ok, so you are stating, that clients timeout while their requests are in the
> The clients timeout because they spend more than timeout in the
> acceptCount/backlog queue waiting for Tomcat to call Socket.accept()
Ok, so you are stating, that clients timeout while their requests are in the
acceptCount/backlog. This is not what I am seeing. See below.
> So we have:
> max
On 19/05/2021 12:24, Paul P Wolf wrote:
Thank you Thomas. I carefully read your explanation. It makes sense to me and
is completely different from what I understood up until this point. With this
new understanding, the problem still persists. Please let me rephrase my issues
in the light of wh
Thank you Thomas. I carefully read your explanation. It makes sense to me and
is completely different from what I understood up until this point. With this
new understanding, the problem still persists. Please let me rephrase my issues
in the light of what I just learned.
To summarize:
- thread
On 19/05/2021 09:28, Paul P Wolf wrote:
In regards to point 5 and 6, let me try to point out my issues with the
documentation and your explanations:
- "Each incoming request requires a thread for the duration of that request. If more
simultaneous requests are received than can be handled by
> Paul,
Thanks for the reply. I am not really much further with my main issue, but I
hope this reply provides more information to you, so you can either clear up my
confusion or see how tomcat doesn't work as intended in my case.
> On 5/18/21 07:44, Paul P Wolf wrote:
> > Hi,
> >
> > I am tryin
17 matches
Mail list logo