You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Santosh Pasi <sp...@diskonnet.com> on 2001/08/11 06:44:00 UTC

Tomcat crashes simultaneous more connection above 990+

Hi everyone,

Can anyone know how much simultaneous connections Tomcat can support, 
where do I need to change the settings to reflect same.  Is no. of max. 
connections support ... is somewhat related with no. of connections to Tomcat.
Yesterday, I tried all combinations .. still as soon as total 
connections .. reaches above 990 .. 997(at most) it crashes Tomcat.  And no more 
process of Tomcat is left.  Although Apache adn other applications are not 
affected.
Is there a no. limitation on child process ... as here child processes 
. increases to some what 1048.. and it crashes.
Same thing i tried on AIX 4.5 ... and it supported above 2600 process 
adn finally it crashed there.
We are looking for 10,000 - 12000 simulatenous connections .. it means 
10000-12000 child process java ... is it problem with java .. we ar using 1.2.2.
Is there any fine tuning that i can do in Tomcat or Apache or Linux?

Regards,
Santosh Pasi



---------------Original Message------------------
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
>Precedence: bulk
>Reply-To: tomcat-user@jakarta.apache.org
>List-Help: <ma...@jakarta.apache.org>
>List-Unsubscribe: <ma...@jakarta.apache.org>
>List-Post: <ma...@jakarta.apache.org>
>To: tomcat-user@jakarta.apache.org
>From: Santosh Pasi<sp...@diskonnet.com>
>Cc: 
>Reply-To: Santosh Pasi<sp...@diskonnet.com>
>Date: Fri, 10 Aug 2001	12:30:04 +0530
>In-Reply-To: message997421139.spasi@diskonnet.com
>Subject: Re: Jakarta crashes simultaneous more connection above 990+
>
>Hi,
>
>Even changing pools setting like
>Increasing the pool size resolved the problem, specifically the
>following parameters (neatly copied from the tomcat users guide)
>
>           <Parameter
>                 name="max_threads"
>                 value="200"/>
>             <Parameter
>                 name="max_spare_threads"
>                 value="20"/>
>             <Parameter
>                 name="min_spare_threads"
>                 value="20" />
>
>The values were arbitrary - I stuck mine up to max_threads = 200,
>max_spare_threads=20, min_spare_threads=20
>and lo - the hang problem  went away.
>
>Even I had used options
>
>TOMCAT_OPTS=" -Xms64m"
>
>Didn't solve the problem.
>
>Still same problem.
>
>Regards,
>Santosh Pasi
>
>---------------Original Message------------------
>Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
>>Precedence: bulk
>>Reply-To: tomcat-user@jakarta.apache.org
>>List-Help: <ma...@jakarta.apache.org>
>>List-Unsubscribe: <ma...@jakarta.apache.org>
>>List-Post: <ma...@jakarta.apache.org>
>>To: tomcat-user@jakarta.apache.org
>>From: Santosh Pasi<sp...@diskonnet.com>
>>Cc: 
>>Reply-To: Santosh Pasi<sp...@diskonnet.com>
>>Date: Fri, 10 Aug 2001	10:55:26 +0530
>>Subject: Jakarta crashes after 900+ simultaneous connection
>>
>>Hi everyone,
>>
>>We are doing some stress testing. My problem is that when number of 
>>connections reaches around 940..980, jakarta crashes with following 

>messages------------------------------------------------------------->SIGSEGV   11*  segmentation violation>>    si_signo [11]: SIGSEGV   11*  segmentation violation
>>    si_errno [0]: Success
>>    si_code [0]: SI_USER [pid: 0, uid: 0]
>>        stackpointer=0x4c558554
>>
>>Full thread dump Classic VM (1.2.2-L, green threads):
>>    "ppp202" (TID:0x40fb7190, sys_thread_t:0x8d0dec0, state:R) prio=5
>>        at java.net.SocketInputStream.socketRead(Native Method)
>>        at java.net.SocketInputStream.read(SocketInputStream.java:86)
>>        at java.net.SocketInputStream.read(SocketInputStream.java:67)
>>        at java.io.InputStreamReader.fill(InputStreamReader.java:159)
>>        at java.io.InputStreamReader.read(InputStreamReader.java:235)
>>        at java.io.BufferedReader.fill(BufferedReader.java:133)
>>        at java.io.BufferedReader.readLine(BufferedReader.java:270)
>>        at java.io.BufferedReader.readLine(BufferedReader.java:325)
>>        at IRCClient.run(IRCClient.java:799)
>>    "bumba174" (TID:0x40f88f90, sys_thread_t:0x8d0b358, state:CW) 
prio=5>>        at java.lang.Thread.sleep(Native Method)
>>        at IRCClient.run(IRCClient.java:765)
>>    "sunny1176" (TID:0x40f75b28, sys_thread_t:0x8d0b930, state:CW) 
>prio=5>        at java.lang.Thread.sleep(Native Method)
>>
>>
>>......
>>......
>>
>>-------------------------------------------------------------
>>
>>We are using redhat 6.2 Linux, kernel 2.2.16, Tomcat-jakarta-3.2.1, 
>>apache 1.3.14.
>>Hope to get some reply.
>>
>>Regards,
>>Santosh Pasi
>>
>>
>
>


Re: Tomcat crashes simultaneous more connection above 990+

Posted by Barnabas Yohannes <yo...@hotmail.com>.
Looks, like my webpage at tomcat is crashing because of many people trying
to access the page simultaneously.  Where in tomcat do you check to see how
many concurrent connections are connected?

----- Original Message -----
From: "Leigh Wanstead" <le...@softtech.co.nz>
To: <to...@jakarta.apache.org>; <ar...@eha.net>
Sent: Tuesday, August 14, 2001 4:26 PM
Subject: Re: Tomcat crashes simultaneous more connection above 990+


> Does anyone try to apply that theory on Tomcat or Jetty or JBoss?
>
>
> ----- Original Message -----
> From: "Aravind Naidu" <ar...@eha.net>
> To: <to...@jakarta.apache.org>
> Sent: Saturday, August 11, 2001 5:50 PM
> Subject: RE: Tomcat crashes simultaneous more connection above 990+
>
>
> > More like a limitation of your JVM on your platform.
> > Look at the Volano benchmarks on network scalability.
> > http://www.volano.com/report/index.html
> >
> >
> > -----Original Message-----
> > From: Santosh Pasi [mailto:spasi@diskonnet.com]
> > Sent: Monday, 1 January 1601 08:00
> > To: tomcat-user@jakarta.apache.org
> > Subject: Tomcat crashes simultaneous more connection above 990+
> >
> >
> > Hi everyone,
> >
> > Can anyone know how much simultaneous connections Tomcat can support,
> > where do I need to change the settings to reflect same.  Is no. of max.
> > connections support ... is somewhat related with no. of connections to
> > Tomcat.
> > Yesterday, I tried all combinations .. still as soon as total
> > connections .. reaches above 990 .. 997(at most) it crashes Tomcat.  And
> no
> > more
> > process of Tomcat is left.  Although Apache adn other applications are
not
> > affected.
> > Is there a no. limitation on child process ... as here child processes
> > . increases to some what 1048.. and it crashes.
> > Same thing i tried on AIX 4.5 ... and it supported above 2600 process
> > adn finally it crashed there.
> > We are looking for 10,000 - 12000 simulatenous connections .. it means
> > 10000-12000 child process java ... is it problem with java .. we ar
using
> > 1.2.2.
> > Is there any fine tuning that i can do in Tomcat or Apache or Linux?
> >
> > Regards,
> > Santosh Pasi
> >
> >
> >
> > ---------------Original Message------------------
> > Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
> > >Precedence: bulk
> > >Reply-To: tomcat-user@jakarta.apache.org
> > >List-Help: <ma...@jakarta.apache.org>
> > >List-Unsubscribe: <ma...@jakarta.apache.org>
> > >List-Post: <ma...@jakarta.apache.org>
> > >To: tomcat-user@jakarta.apache.org
> > >From: Santosh Pasi<sp...@diskonnet.com>
> > >Cc:
> > >Reply-To: Santosh Pasi<sp...@diskonnet.com>
> > >Date: Fri, 10 Aug 2001 12:30:04 +0530
> > >In-Reply-To: message997421139.spasi@diskonnet.com
> > >Subject: Re: Jakarta crashes simultaneous more connection above 990+
> > >
> > >Hi,
> > >
> > >Even changing pools setting like
> > >Increasing the pool size resolved the problem, specifically the
> > >following parameters (neatly copied from the tomcat users guide)
> > >
> > >           <Parameter
> > >                 name="max_threads"
> > >                 value="200"/>
> > >             <Parameter
> > >                 name="max_spare_threads"
> > >                 value="20"/>
> > >             <Parameter
> > >                 name="min_spare_threads"
> > >                 value="20" />
> > >
> > >The values were arbitrary - I stuck mine up to max_threads = 200,
> > >max_spare_threads=20, min_spare_threads=20
> > >and lo - the hang problem  went away.
> > >
> > >Even I had used options
> > >
> > >TOMCAT_OPTS=" -Xms64m"
> > >
> > >Didn't solve the problem.
> > >
> > >Still same problem.
> > >
> > >Regards,
> > >Santosh Pasi
> > >
> > >---------------Original Message------------------
> > >Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
> > >>Precedence: bulk
> > >>Reply-To: tomcat-user@jakarta.apache.org
> > >>List-Help: <ma...@jakarta.apache.org>
> > >>List-Unsubscribe: <ma...@jakarta.apache.org>
> > >>List-Post: <ma...@jakarta.apache.org>
> > >>To: tomcat-user@jakarta.apache.org
> > >>From: Santosh Pasi<sp...@diskonnet.com>
> > >>Cc:
> > >>Reply-To: Santosh Pasi<sp...@diskonnet.com>
> > >>Date: Fri, 10 Aug 2001 10:55:26 +0530
> > >>Subject: Jakarta crashes after 900+ simultaneous connection
> > >>
> > >>Hi everyone,
> > >>
> > >>We are doing some stress testing. My problem is that when number of
> > >>connections reaches around 940..980, jakarta crashes with following
> >
> >
>
>messages------------------------------------------------------------->SIGSE
> > GV   11*  segmentation violation>>    si_signo [11]: SIGSEGV   11*
> > segmentation violation
> > >>    si_errno [0]: Success
> > >>    si_code [0]: SI_USER [pid: 0, uid: 0]
> > >>        stackpointer=0x4c558554
> > >>
> > >>Full thread dump Classic VM (1.2.2-L, green threads):
> > >>    "ppp202" (TID:0x40fb7190, sys_thread_t:0x8d0dec0, state:R) prio=5
> > >>        at java.net.SocketInputStream.socketRead(Native Method)
> > >>        at java.net.SocketInputStream.read(SocketInputStream.java:86)
> > >>        at java.net.SocketInputStream.read(SocketInputStream.java:67)
> > >>        at java.io.InputStreamReader.fill(InputStreamReader.java:159)
> > >>        at java.io.InputStreamReader.read(InputStreamReader.java:235)
> > >>        at java.io.BufferedReader.fill(BufferedReader.java:133)
> > >>        at java.io.BufferedReader.readLine(BufferedReader.java:270)
> > >>        at java.io.BufferedReader.readLine(BufferedReader.java:325)
> > >>        at IRCClient.run(IRCClient.java:799)
> > >>    "bumba174" (TID:0x40f88f90, sys_thread_t:0x8d0b358, state:CW)
> > prio=5>>        at java.lang.Thread.sleep(Native Method)
> > >>        at IRCClient.run(IRCClient.java:765)
> > >>    "sunny1176" (TID:0x40f75b28, sys_thread_t:0x8d0b930, state:CW)
> > >prio=5>        at java.lang.Thread.sleep(Native Method)
> > >>
> > >>
> > >>......
> > >>......
> > >>
> > >>-------------------------------------------------------------
> > >>
> > >>We are using redhat 6.2 Linux, kernel 2.2.16, Tomcat-jakarta-3.2.1,
> > >>apache 1.3.14.
> > >>Hope to get some reply.
> > >>
> > >>Regards,
> > >>Santosh Pasi
> > >>
> > >>
> > >
> > >
> >
> >
>
>
>

Re: Tomcat crashes simultaneous more connection above 990+

Posted by Leigh Wanstead <le...@softtech.co.nz>.
Does anyone try to apply that theory on Tomcat or Jetty or JBoss?


----- Original Message -----
From: "Aravind Naidu" <ar...@eha.net>
To: <to...@jakarta.apache.org>
Sent: Saturday, August 11, 2001 5:50 PM
Subject: RE: Tomcat crashes simultaneous more connection above 990+


> More like a limitation of your JVM on your platform.
> Look at the Volano benchmarks on network scalability.
> http://www.volano.com/report/index.html
>
>
> -----Original Message-----
> From: Santosh Pasi [mailto:spasi@diskonnet.com]
> Sent: Monday, 1 January 1601 08:00
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat crashes simultaneous more connection above 990+
>
>
> Hi everyone,
>
> Can anyone know how much simultaneous connections Tomcat can support,
> where do I need to change the settings to reflect same.  Is no. of max.
> connections support ... is somewhat related with no. of connections to
> Tomcat.
> Yesterday, I tried all combinations .. still as soon as total
> connections .. reaches above 990 .. 997(at most) it crashes Tomcat.  And
no
> more
> process of Tomcat is left.  Although Apache adn other applications are not
> affected.
> Is there a no. limitation on child process ... as here child processes
> . increases to some what 1048.. and it crashes.
> Same thing i tried on AIX 4.5 ... and it supported above 2600 process
> adn finally it crashed there.
> We are looking for 10,000 - 12000 simulatenous connections .. it means
> 10000-12000 child process java ... is it problem with java .. we ar using
> 1.2.2.
> Is there any fine tuning that i can do in Tomcat or Apache or Linux?
>
> Regards,
> Santosh Pasi
>
>
>
> ---------------Original Message------------------
> Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
> >Precedence: bulk
> >Reply-To: tomcat-user@jakarta.apache.org
> >List-Help: <ma...@jakarta.apache.org>
> >List-Unsubscribe: <ma...@jakarta.apache.org>
> >List-Post: <ma...@jakarta.apache.org>
> >To: tomcat-user@jakarta.apache.org
> >From: Santosh Pasi<sp...@diskonnet.com>
> >Cc:
> >Reply-To: Santosh Pasi<sp...@diskonnet.com>
> >Date: Fri, 10 Aug 2001 12:30:04 +0530
> >In-Reply-To: message997421139.spasi@diskonnet.com
> >Subject: Re: Jakarta crashes simultaneous more connection above 990+
> >
> >Hi,
> >
> >Even changing pools setting like
> >Increasing the pool size resolved the problem, specifically the
> >following parameters (neatly copied from the tomcat users guide)
> >
> >           <Parameter
> >                 name="max_threads"
> >                 value="200"/>
> >             <Parameter
> >                 name="max_spare_threads"
> >                 value="20"/>
> >             <Parameter
> >                 name="min_spare_threads"
> >                 value="20" />
> >
> >The values were arbitrary - I stuck mine up to max_threads = 200,
> >max_spare_threads=20, min_spare_threads=20
> >and lo - the hang problem  went away.
> >
> >Even I had used options
> >
> >TOMCAT_OPTS=" -Xms64m"
> >
> >Didn't solve the problem.
> >
> >Still same problem.
> >
> >Regards,
> >Santosh Pasi
> >
> >---------------Original Message------------------
> >Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
> >>Precedence: bulk
> >>Reply-To: tomcat-user@jakarta.apache.org
> >>List-Help: <ma...@jakarta.apache.org>
> >>List-Unsubscribe: <ma...@jakarta.apache.org>
> >>List-Post: <ma...@jakarta.apache.org>
> >>To: tomcat-user@jakarta.apache.org
> >>From: Santosh Pasi<sp...@diskonnet.com>
> >>Cc:
> >>Reply-To: Santosh Pasi<sp...@diskonnet.com>
> >>Date: Fri, 10 Aug 2001 10:55:26 +0530
> >>Subject: Jakarta crashes after 900+ simultaneous connection
> >>
> >>Hi everyone,
> >>
> >>We are doing some stress testing. My problem is that when number of
> >>connections reaches around 940..980, jakarta crashes with following
>
>
>messages------------------------------------------------------------->SIGSE
> GV   11*  segmentation violation>>    si_signo [11]: SIGSEGV   11*
> segmentation violation
> >>    si_errno [0]: Success
> >>    si_code [0]: SI_USER [pid: 0, uid: 0]
> >>        stackpointer=0x4c558554
> >>
> >>Full thread dump Classic VM (1.2.2-L, green threads):
> >>    "ppp202" (TID:0x40fb7190, sys_thread_t:0x8d0dec0, state:R) prio=5
> >>        at java.net.SocketInputStream.socketRead(Native Method)
> >>        at java.net.SocketInputStream.read(SocketInputStream.java:86)
> >>        at java.net.SocketInputStream.read(SocketInputStream.java:67)
> >>        at java.io.InputStreamReader.fill(InputStreamReader.java:159)
> >>        at java.io.InputStreamReader.read(InputStreamReader.java:235)
> >>        at java.io.BufferedReader.fill(BufferedReader.java:133)
> >>        at java.io.BufferedReader.readLine(BufferedReader.java:270)
> >>        at java.io.BufferedReader.readLine(BufferedReader.java:325)
> >>        at IRCClient.run(IRCClient.java:799)
> >>    "bumba174" (TID:0x40f88f90, sys_thread_t:0x8d0b358, state:CW)
> prio=5>>        at java.lang.Thread.sleep(Native Method)
> >>        at IRCClient.run(IRCClient.java:765)
> >>    "sunny1176" (TID:0x40f75b28, sys_thread_t:0x8d0b930, state:CW)
> >prio=5>        at java.lang.Thread.sleep(Native Method)
> >>
> >>
> >>......
> >>......
> >>
> >>-------------------------------------------------------------
> >>
> >>We are using redhat 6.2 Linux, kernel 2.2.16, Tomcat-jakarta-3.2.1,
> >>apache 1.3.14.
> >>Hope to get some reply.
> >>
> >>Regards,
> >>Santosh Pasi
> >>
> >>
> >
> >
>
>



RE: Tomcat crashes simultaneous more connection above 990+

Posted by Aravind Naidu <ar...@eha.net>.
More like a limitation of your JVM on your platform.
Look at the Volano benchmarks on network scalability.
http://www.volano.com/report/index.html


-----Original Message-----
From: Santosh Pasi [mailto:spasi@diskonnet.com]
Sent: Monday, 1 January 1601 08:00
To: tomcat-user@jakarta.apache.org
Subject: Tomcat crashes simultaneous more connection above 990+


Hi everyone,

Can anyone know how much simultaneous connections Tomcat can support,
where do I need to change the settings to reflect same.  Is no. of max.
connections support ... is somewhat related with no. of connections to
Tomcat.
Yesterday, I tried all combinations .. still as soon as total
connections .. reaches above 990 .. 997(at most) it crashes Tomcat.  And no
more
process of Tomcat is left.  Although Apache adn other applications are not
affected.
Is there a no. limitation on child process ... as here child processes
. increases to some what 1048.. and it crashes.
Same thing i tried on AIX 4.5 ... and it supported above 2600 process
adn finally it crashed there.
We are looking for 10,000 - 12000 simulatenous connections .. it means
10000-12000 child process java ... is it problem with java .. we ar using
1.2.2.
Is there any fine tuning that i can do in Tomcat or Apache or Linux?

Regards,
Santosh Pasi



---------------Original Message------------------
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
>Precedence: bulk
>Reply-To: tomcat-user@jakarta.apache.org
>List-Help: <ma...@jakarta.apache.org>
>List-Unsubscribe: <ma...@jakarta.apache.org>
>List-Post: <ma...@jakarta.apache.org>
>To: tomcat-user@jakarta.apache.org
>From: Santosh Pasi<sp...@diskonnet.com>
>Cc:
>Reply-To: Santosh Pasi<sp...@diskonnet.com>
>Date: Fri, 10 Aug 2001	12:30:04 +0530
>In-Reply-To: message997421139.spasi@diskonnet.com
>Subject: Re: Jakarta crashes simultaneous more connection above 990+
>
>Hi,
>
>Even changing pools setting like
>Increasing the pool size resolved the problem, specifically the
>following parameters (neatly copied from the tomcat users guide)
>
>           <Parameter
>                 name="max_threads"
>                 value="200"/>
>             <Parameter
>                 name="max_spare_threads"
>                 value="20"/>
>             <Parameter
>                 name="min_spare_threads"
>                 value="20" />
>
>The values were arbitrary - I stuck mine up to max_threads = 200,
>max_spare_threads=20, min_spare_threads=20
>and lo - the hang problem  went away.
>
>Even I had used options
>
>TOMCAT_OPTS=" -Xms64m"
>
>Didn't solve the problem.
>
>Still same problem.
>
>Regards,
>Santosh Pasi
>
>---------------Original Message------------------
>Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
>>Precedence: bulk
>>Reply-To: tomcat-user@jakarta.apache.org
>>List-Help: <ma...@jakarta.apache.org>
>>List-Unsubscribe: <ma...@jakarta.apache.org>
>>List-Post: <ma...@jakarta.apache.org>
>>To: tomcat-user@jakarta.apache.org
>>From: Santosh Pasi<sp...@diskonnet.com>
>>Cc:
>>Reply-To: Santosh Pasi<sp...@diskonnet.com>
>>Date: Fri, 10 Aug 2001	10:55:26 +0530
>>Subject: Jakarta crashes after 900+ simultaneous connection
>>
>>Hi everyone,
>>
>>We are doing some stress testing. My problem is that when number of
>>connections reaches around 940..980, jakarta crashes with following

>messages------------------------------------------------------------->SIGSE
GV   11*  segmentation violation>>    si_signo [11]: SIGSEGV   11*
segmentation violation
>>    si_errno [0]: Success
>>    si_code [0]: SI_USER [pid: 0, uid: 0]
>>        stackpointer=0x4c558554
>>
>>Full thread dump Classic VM (1.2.2-L, green threads):
>>    "ppp202" (TID:0x40fb7190, sys_thread_t:0x8d0dec0, state:R) prio=5
>>        at java.net.SocketInputStream.socketRead(Native Method)
>>        at java.net.SocketInputStream.read(SocketInputStream.java:86)
>>        at java.net.SocketInputStream.read(SocketInputStream.java:67)
>>        at java.io.InputStreamReader.fill(InputStreamReader.java:159)
>>        at java.io.InputStreamReader.read(InputStreamReader.java:235)
>>        at java.io.BufferedReader.fill(BufferedReader.java:133)
>>        at java.io.BufferedReader.readLine(BufferedReader.java:270)
>>        at java.io.BufferedReader.readLine(BufferedReader.java:325)
>>        at IRCClient.run(IRCClient.java:799)
>>    "bumba174" (TID:0x40f88f90, sys_thread_t:0x8d0b358, state:CW)
prio=5>>        at java.lang.Thread.sleep(Native Method)
>>        at IRCClient.run(IRCClient.java:765)
>>    "sunny1176" (TID:0x40f75b28, sys_thread_t:0x8d0b930, state:CW)
>prio=5>        at java.lang.Thread.sleep(Native Method)
>>
>>
>>......
>>......
>>
>>-------------------------------------------------------------
>>
>>We are using redhat 6.2 Linux, kernel 2.2.16, Tomcat-jakarta-3.2.1,
>>apache 1.3.14.
>>Hope to get some reply.
>>
>>Regards,
>>Santosh Pasi
>>
>>
>
>