Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 54461 invoked by uid 500); 10 Aug 2001 07:58:12 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 54452 invoked from network); 10 Aug 2001 07:58:12 -0000 Received: from unknown (HELO webmail.diskonnet.com) (qmailr@206.50.5.212) by h31.sny.collab.net with SMTP; 10 Aug 2001 07:58:12 -0000 Received: (qmail 7253 invoked from network); 10 Aug 2001 07:00:04 -0000 Received: from webmail.diskonnet.com (HELO localhost) (vuser@[206.50.5.212]) (envelope-sender ) by webmail.diskonnet.com (qmail-ldap-1.03) with SMTP for ; 10 Aug 2001 07:00:04 -0000 To: tomcat-user@jakarta.apache.org From: Santosh Pasi Cc: X-Mailer: Perl Mail::Sender Version 0.6.7 Jan Krynicky Czech Republic reply-to: Santosh Pasi Message-ID: 997426804spasi@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+ X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi, Even changing pools setting like Increasing the pool size resolved the problem, specifically the following parameters (neatly copied from the tomcat users guide) 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: >List-Unsubscribe: >List-Post: >To: tomcat-user@jakarta.apache.org >From: Santosh Pasi >Cc: >Reply-To: Santosh Pasi >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 > >