Yes, I also think it should act like this, but it did not.
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Monday, January 16, 2017 2:33 PM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2017 15:19, Christopher Schultz
Yes, I think thread count should be reduced when those threads are idle
Is this right? Or it will not reduced?
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, January 16, 2017 2:20 PM
To: Tomcat Users List
Subject: Re: FW: tomcat 8080 thre
We're having a similar issues with our numberous Tomcat instances.
Our connector config look like this.
Sometime, the number of active connection would jump very high (up to
190), due to some external issues (database lock, etc) and threads would
accumulate.
Even though a connectionTimeo
Hi,
2017-01-09 13:57 GMT+02:00 Mark Thomas :
>
> All,
>
> There is the opportunity (if we can pull it together as a community) to
> run a dedicated Tomcat conference alongside ApacheCon NA 2017. The dates
> are May 16 to 18.
>
> The call for papers closes on Feb 11 so we have around a month to get
On 16.01.2017 15:19, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
There are your only active s:
On 1/14/17 1:30 AM, smith wrote:
[snip]
You have not changed any settings from the default. What makes you
think that your thread count should be reduced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Smith,
There are your only active s:
On 1/14/17 1:30 AM, smith wrote:
> connectionTimeout="2" redirectPort="8443" />
>
> [snip]
>
>
You have not changed any settings from the default. What makes you
think that your thread count should be r
Mark
> "What topic(s) need to be covered in a Tomcat conference to make it
> as easy as possible to get your employer to pay for you to attend?"
OK, you asked for it. :-)
- The best and worst moments in Tomcat history.
Specific examples. Memorable events. Could be just for the year so the sam
On 16.01.2017 11:10, smith wrote:
We has same problem on dev env that no any traffic to the serive,
Ah. That is /new/ information, which may change the suggestions below.
It looks like you should really find out what these threads are doing, probably by doing a
few thread dumps.
See here e.g.
We has same problem on dev env that no any traffic to the serive, will try on
dev first
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Monday, January 16, 2017 10:08 AM
To: users@tomcat.apache.org
Subject: Re: FW: tomcat 8080 thread not reduced
On 16.01.2
On 16.01.2017 09:50, smith wrote:
Busy one is process customer request, do not know what non-busy one is doing,
always keep 120 for many days. I don't think 20s timeout will not cause so long
connection
-smith
And did you actually try it ?
We do not know your website or your application, so
Trying to launch Tomcat 8.0.39 embedded with a datasource configured, I get
this error:
/Failed to log into the database: Name [java:/comp/env/myDsName] is not bound
in this Context. Unable to find [java:]./
I'm configuring the default Tomcat ContactFactory. This is the relevant source:
Busy one is process customer request, do not know what non-busy one is doing,
always keep 120 for many days. I don't think 20s timeout will not cause so long
connection
-smith
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Monday, January 16, 2017 8:33 A
On 16.01.2017 03:41, Smith Hua wrote:
actually there is not much busy threads, less tahn 10,so i think this parameter
may has nothing to do with this
It depends on what you call "busy". What are the busy ones doing ? and what are the
non-busy ones doing ?
--
从myMail的Android专用app所发送 星期一,
13 matches
Mail list logo
