-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vicky,
On 10/25/12 12:22 AM, vicky007aggar...@yahoo.co.in wrote:
> In my environment i am using Apache 2.2 & Tomcat 6.0 version .
>
> @ Both of these are multi-threaded right?
Tomcat is always multi-threaded capable but you could always configure
it
Christopher u r a GEM.
Thanks christopher for explaining the basics so passionately & nicely.
I have some more trivial questions pls share your brilliance on that as well &
help many more like me to learn the concepts ;-
In my environment i am using Apache 2.2 & Tomcat 6.0 version .
@ Both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 10/24/12 3:03 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: Max Threads - Worker Threads clarification
>
>> It's a little more complicated tha
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Max Threads - Worker Threads clarification
> It's a little more complicated than that, because a threaded Tomcat
> can have multiple connections per child process.
One presumes you meant "http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vivek,
On 10/24/12 12:21 PM, vivek aggarwal wrote:
> I have following understanding with regards to your trailing mail
> comments ,pls do correct me if that's not correct :-
>
> In workers.properties (Apache end) we have directive called
> "connec
ist
Sent: Wednesday, 24 October 2012 7:17 PM
Subject: Re: Max Threads - Worker Threads clarification
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
On 10/24/12 8:29 AM, Charles Richard wrote:
> I do use load balancing on our production environment so I'll have
> to check out the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
On 10/24/12 8:29 AM, Charles Richard wrote:
> I do use load balancing on our production environment so I'll have
> to check out the parallel timeout you mention, I don't think I've
> read about this before.
You'll need those values to be the
Hi Chris,
I do use load balancing on our production environment so I'll have to check
out the parallel timeout you mention, I don't think I've read about this
before.
As far as Tomcat hanging, my apologies, I discovered late yesterday that it
was Apache reaching its MaxClients limit and therefore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
On 10/23/12 3:01 PM, Charles Richard wrote:
> I am doing load testing. I'm trying to ensure that our production
> site can handle as much traffic as it possibly can and I'm trying
> to make sure I refine my performance tuning skills on a tes
On 10/23/2012 12:01 PM, Charles Richard wrote:
Hi,
I am doing load testing. I'm trying to ensure that our production site can
handle as much traffic as it possibly can and I'm trying to make sure I
refine my performance tuning skills on a test environment. Here are some
more specifics:
Mod_jk
I'll take Pid's suggestion of trying VisualVM and I've been using Jprofiler
but don't think i was using it correctly. I'll use those and report later.
Thanks for all the help, starting to feel like I'm getting somewhere!
Cheers,
Charles
On Tue, Oct 23, 2012 at 3:53 PM, Pid wrote:
> On 23/10/2
Hi,
I am doing load testing. I'm trying to ensure that our production site can
handle as much traffic as it possibly can and I'm trying to make sure I
refine my performance tuning skills on a test environment. Here are some
more specifics:
Mod_jk is 1.2.31
Settings in workers.properties:
worker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
(Sorry for posting before I read all the follow-ups).
On 10/23/12 2:46 PM, Charles Richard wrote:
> With wc removed, it looked like the following:
>
> tcp0 0 127.0.0.1:8009 127.0.0.1:37744
> ESTABLISHED tcp
On 23/10/2012 19:46, Charles Richard wrote:
> With wc removed, it looked like the following:
>
> tcp0 0 127.0.0.1:8009 127.0.0.1:37744
> ESTABLISHED
> tcp0 0 127.0.0.1:8009 127.0.0.1:36976
> ESTABLISHED
> tcp0 0 127.0.0.1:8009
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles,
On 10/23/12 10:45 AM, Charles Richard wrote:
> I'm testing performance of our Java application in Tomcat (6.0.30)
> and we have maxThreads set to 750. I noticed that when i did a
> netstat -an | grep my_ajp_port, i saw around 860 connections
With wc removed, it looked like the following:
tcp0 0 127.0.0.1:8009 127.0.0.1:37744
ESTABLISHED
tcp0 0 127.0.0.1:8009 127.0.0.1:36976
ESTABLISHED
tcp0 0 127.0.0.1:8009 127.0.0.1:35695
ESTABLISHED
tcp0 0 127
Hi Charles,
If you want to really see how many are busy, perhaps qualify the command as:
netstat -an | grep 8009 | grep ESTABLISH | wc -l
Some connections may be in CLOSE_WAIT or TIME_WAIT states, waiting to be
closed.
Thanks.
-Shanti
On Tue, Oct 23, 2012 at 12:10 PM, C
On Oct 23, 2012, at 12:10 PM, Charles Richard wrote:
> Hi,
>
> Thanks for the reply!
>
> The command was the following:
>
> [root@mysandbox tmp]# netstat -an | grep 8009 | wc
>8565136 76184
What output do you get if you remove the "wc" command?
> How should i interpret this? I tho
Hi,
Thanks for the reply!
The command was the following:
[root@mysandbox tmp]# netstat -an | grep 8009 | wc
8565136 76184
How should i interpret this? I thought this meant that 856 threads were
open while my MaxThreads is 750. I'm trying to understand if all my
workerThreads are bus
>> Hi,
>>
>> I'm testing performance of our Java application in Tomcat (6.0.30) and we
>> have maxThreads set to 750. I noticed that when i did a netstat -an | grep
>> my_ajp_port, i saw around 860 connections.
That does not necessarily mean that you have 860 threads running. What are you
tr
I also facing similiar issues and what I'm noting is that almost every
question is either about tomcat's perfomance and optimization or minimal
setup. It woul be wonderful if exists some sort of tutorial or best
pratices about that point...
I'll track this thread too...
2012/10/23 Charles Richard
21 matches
Mail list logo
