Jerry,
On 6/21/21 14:54, Jerry Malcolm wrote:
I have a TC instance running on an EC2 in an AWS Autoscaling group. I
have a database with 500 max connections. The default EC2 count is 2
instances in the autoscaling group. I guess that means that I should
set the Tomcat resource config
I have a TC instance running on an EC2 in an AWS Autoscaling group. I
have a database with 500 max connections. The default EC2 count is 2
instances in the autoscaling group. I guess that means that I should
set the Tomcat resource config for this datasource to be maxTotal = 250,
so if both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 8/27/20 18:14, David wrote:
>> I used the http to 8080 in order to read the Tomcat webmanager
>> stats. I originally had issues with the JVM being too small,
>> running out of memory, CPU spiking, threads maxing out, and
>> whole system
On Thu, Aug 27, 2020 at 4:30 PM Christopher Schultz
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> David,
>
> On 8/27/20 17:14, David wrote:
> > Thank you all for the replies!
> >
> > On Thu, Aug 27, 2020 at 3:53 PM Christopher Schultz
> > wrote:
> >>
> > David,
> >
> > On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 8/27/20 17:14, David wrote:
> Thank you all for the replies!
>
> On Thu, Aug 27, 2020 at 3:53 PM Christopher Schultz
> wrote:
>>
> David,
>
> On 8/27/20 13:57, David wrote:
On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz
Thank you all for the replies!
On Thu, Aug 27, 2020 at 3:53 PM Christopher Schultz
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> David,
>
> On 8/27/20 13:57, David wrote:
> > On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz
> > wrote:
> >>
> > David,
> >
> > On 8/27/20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Felix,
On 8/27/20 16:09, Felix Schumacher wrote:
>
> Am 27.08.20 um 19:35 schrieb Christopher Schultz:
>> David,
>>
>> On 8/27/20 10:48, David wrote:
>>> In the last two weeks I've had two occurrences where a single
>>> CentOS 7 production server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 8/27/20 13:57, David wrote:
> On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz
> wrote:
>>
> David,
>
> On 8/27/20 10:48, David wrote:
In the last two weeks I've had two occurrences where a
single CentOS 7 production server
Am 27.08.20 um 19:35 schrieb Christopher Schultz:
> David,
>
> On 8/27/20 10:48, David wrote:
> > In the last two weeks I've had two occurrences where a single
> > CentOS 7 production server hosting a public webpage has become
> > unresponsive. The first time, all 300 available
> >
On 27/08/2020 18:57, David wrote:
> On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz
> wrote:
Is there a graceful way to script the termination of threads in
case Tomcat isn't able to for whatever reason?
>
> Not really.
What you can do is take a thread dump when this happens so
On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> David,
>
> On 8/27/20 10:48, David wrote:
> > In the last two weeks I've had two occurrences where a single
> > CentOS 7 production server hosting a public webpage has become
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 8/27/20 10:48, David wrote:
> In the last two weeks I've had two occurrences where a single
> CentOS 7 production server hosting a public webpage has become
> unresponsive. The first time, all 300 available
> "https-jsse-nio-8443" threads
In the last two weeks I've had two occurrences where a single CentOS 7
production server hosting a public webpage has become unresponsive. The
first time, all 300 available "https-jsse-nio-8443" threads were consumed,
with the max age being around 45minutes, and all in a "S" status. This time
Martin Gainty wrote:
in $TOMCAT_HOME/conf/server.xml Connector implements the acceptCount
attribute
http://tomcat.apache.org/tomcat-4.1-doc/config/coyote.html
acceptCount is not the right attribute to do this. That is also the 4.1
doc. The OP didn't say what version they were using.
From:
content contained within this
transmission.
Date: Sun, 12 Oct 2008 17:27:08 -0700
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Subject: Max connections
How can I limit number of connections to Tomcat server from outside
world? Like jboss has jmx console does tomcat has something
From: Mohit Anchlia [mailto:[EMAIL PROTECTED]
Subject: Re: Max connections
I didn't understand the description of attribute
maxKeepAliveRequests, it says:
The maximum number of HTTP requests which can be pipelined until the
connection is closed by the server.
Does it mean total number
I am using tomcat 6
On Sun, Oct 12, 2008 at 11:29 PM, Mark Thomas [EMAIL PROTECTED] wrote:
Martin Gainty wrote:
in $TOMCAT_HOME/conf/server.xml Connector implements the acceptCount
attribute
http://tomcat.apache.org/tomcat-4.1-doc/config/coyote.html
acceptCount is not the right attribute
so if I can use JMX can I also set debug level dynamically? I am using
tomcat 6.0
On Mon, Oct 13, 2008 at 9:55 AM, Mohit Anchlia [EMAIL PROTECTED] wrote:
I am using tomcat 6
On Sun, Oct 12, 2008 at 11:29 PM, Mark Thomas [EMAIL PROTECTED] wrote:
Martin Gainty wrote:
in
How can I limit number of connections to Tomcat server from outside
world? Like jboss has jmx console does tomcat has something like that?
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL
PROTECTED]
To: users@tomcat.apache.org
Subject: Max connections
How can I limit number of connections to Tomcat server from outside
world? Like jboss has jmx console does tomcat has something like that?
-
To start a new topic
17:27:08 -0700
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Subject: Max connections
How can I limit number of connections to Tomcat server from outside
world? Like jboss has jmx console does tomcat has something like
21 matches
Mail list logo
